Repository navigation
feat: script only components - #2311
Draft
vados-cosmonic wants to merge 6 commits into
Draft
vados-cosmonic wants to merge 6 commits into
vados-cosmonic wants to merge 6 commits into
Conversation
vados-cosmonic
force-pushed
the
feat/script-only-components
branch
3 times, most recently
from
October 24, 2026 07:06
104e0bc to
1f6bcbb
Compare
vados-cosmonic
force-pushed
the
feat/script-only-components
branch
from
October 25, 2026 11:25
1f6bcbb to
963f6b7
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the ability to generate script only components when using
jco componentize.The goal of this feature is to be able to quickly load and execute components that contain only JS scripts (thus are very light).
Under script-only components, one or more JS files can be componentized against one or more WIT worlds (you can include WITs that are not covered by the actual JS files yet).
Reusing the same engine of course introduces new security risks, as engine state is not necessarily reset between runs (current engines don't really support that explicitly, though it could be added with or without upstream support), but the assumption is that this approach is used in a context where that isn't an issue (e.g. engine-per-tenant).