@lvce-editor/extension-management-worker 4.74.4 → 4.75.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/dist/extensionManagementWorkerMain.js +1089 -978
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,3 +1,11 @@
|
|
|
1
1
|
# Extension Management Worker
|
|
2
2
|
|
|
3
3
|
Webworker for the Extension Management functionality in Lvce Editor.
|
|
4
|
+
|
|
5
|
+
## Remote workspace processes
|
|
6
|
+
|
|
7
|
+
Node RPC declarations run on the local application host by default. A declaration can opt into the workspace host with `"onRemote": "runOnRemote"`. In a remote workspace, extension management transfers its MessagePort to the isolated extension that declares `workspaceTransport: { scheme, command }` for that URI scheme. The transport command receives `(workspaceUri, type, port, params)`, where `params` contains the validated calling extension ID and declared RPC ID for `extension-node-process`. Terminals use `terminal-process` without extension IDs.
|
|
8
|
+
|
|
9
|
+
Transport commands are reserved for extension management and cannot be invoked as ordinary extension commands. The transport extension owns authentication, WebSockets, and connection disposal. Disabled or missing transports fail without launching a local replacement process. File workspaces retain local Node RPC connections.
|
|
10
|
+
|
|
11
|
+
Transports can additionally declare a `requestCommand` for `text-search`, `file-search`, and `terminal-options` requests. These receive the workspace URI, request type, and request arguments, and return the result through the extension RPC.
|