What if Joyride could contribute commands and configuration etcetera?

[PEZ]

Joyride offers amazing access to the runtime parts of the VS Code API, at the REPL. There is no access to the contributes object of Joyride's extension manifest. Meaning the user can't contribute commands, configurations (i.e. new settings), grammars, theme and a ton of such things. (Some contribution points have dynamic API:s.)

However, if Joyride would zip together a VSIX and tell vscode to install it, then that would be a way to make this happen. VS Code installs and loads extensions w/o reload required.

The process would be something like that:

1. a script calls a function to declare commands, keyboard shortcuts, etcetera
2. this causes an extension to be created and loaded
3. ”normal” user scripts register the commands

BOOM. (No idea if updates of this extension would require reloads, but if if it does it would be fine.)

And/or:

Joyride has a command for packaging a set of scripts as an extension. This extension can be distributed as any other extension can. It can either:

1. Require that the user of the packed extension has Joyride installed
2. Declare Joyride as a dependency in the extension manifest
3. Bundle enough of the Joyride runtime to be self-contained

For some extensions this would be a super nice dev environment. For some extensions the performance wouldn't be enough. But Joyride could be great for the prototyping. It is also possible to imagine an eject option that creates a shadow-cljs extension project from the Joyride sources.