asar is a utility and may require access to arbitrary files from anywhere of the file system. Particularly when inspecting archives already installed that will exist outside of $HOME
“may require access” could be said of almost any application that needs filesystem access, but we have plenty of examples (eg, brave, chromium, gedit, etc) that use strict mode that also require filesystem access. I’m unfamiliar with asar: what about it makes it different from strictly confined snaps such that it requires classic? Put another way, what are typical use cases that make it not work with strict mode?
Providing specific use cases that are making people use classic over strict will help us better understand how to improve the system in the future.
asar is a command line utility, much like tar for creating and extracting archives. It is the default bundling tool/library used in Electron applications.
Thank you, that is helpful. As a command line archive utility, that use case is understood for classic.
You mentioned that it is used by electron applications, but I’m confused by this detail. Wouldn’t an electron snap just embed asar? Or are you saying it is primarily used to build electron applications (in which case, wouldn’t things to bundle in the electron app already be in home or removable-media?)? Something else?
asar is a command line implementation of the asar archive format. The asar library is used by Electron to create the application bundles. The asar snap is really just exposing the asar utility, which doesn’t feature in the deb archives.
@jdstrand This snap package can be published by committers of the Electron project, who are usually GitHub employees or third party contributors that have been verified by GitHub.