Skip to content

Conversation

@tschneidereit
Copy link
Member

StarlingMonkey supports a growing number of arguments in addition to the filename of the script to run. This commit adds support for passing those arguments through when componentizing.

I think it'll eventually make sense to expose some of these arguments more explicitly, but providing this option allows us to evolve the interfaces separately, similar to how e.g. clang supports passing linker arguments, or cargo supports passing rustc arguments.

@tschneidereit
Copy link
Member Author

The reason I'm opening this PR now is that this will enable us to use the source debugging feature we just landed in StarlingMonkey without a custom version of ComponentizeJS

tschneidereit and others added 2 commits February 21, 2025 11:54
StarlingMonkey supports a growing number of arguments in addition to the filename of the script to run. This commit adds support for passing those arguments through when componentizing.

I think it'll eventually make sense to expose some of these arguments more explicitly, but providing this option allows us to evolve the interfaces separately, similar to how e.g. clang supports passing linker arguments, or cargo supports passing rustc arguments.
@guybedford
Copy link

Just updated the types.d.ts and docs files as well here. This approach looks great thanks.

@guybedford guybedford merged commit c284639 into bytecodealliance:main Feb 21, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants