Protected ReadonlyenvProtected ReadonlyfileProtected ReadonlylocalFallback for withStoreLock when the Web Locks API is unavailable.
Protected ReadonlyloggerProtectedmissingProtected ReadonlypluginProtectedgetWhere the given kind of values is kept, or undefined if there's nowhere to keep them -
e.g. workspace state while no workspace is open.
ProtectedgetThe Web Locks API of this browsing context, or undefined in an insecure context or an older browser.
Deploy a plugin.
Optionaltype: PluginType
whether a plugin is installed by a system or a user, defaults to a user
Optionaloptions: PluginDeployOptionsProtectedreadReads the values of store. Not cached: other tabs write the same file. Must be called
while holding the lock for store, see withStoreLock.
ProtectedrequestRequests name from locks and runs callback once granted, same as LockManager.request().
LockGrantedCallback is typed as (lock: Lock | null) => T, which doesn't account for an
async or never-settling callback even though the API itself supports and awaits one, hence
the cast. Kept as its own method so a subclass or test can swap the lock implementation.
ProtectedwithProtectedwriteWrites values to store, putting previousContent back if that fails. Must be called
while holding the lock for store, see withStoreLock.
Plugins of a browser-only application are deployed at build time, so they can't be installed, uninstalled, enabled or disabled at runtime. The queries just report an empty result instead of failing, so callers like the plugin view still have something to render.
The plugin key-value storage backing
ExtensionContext.globalStateandExtensionContext.workspaceStatelives in JSON files under the config directory on the browser-local file system, laid out like the backend does.