Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jco componentize --wasi-command / --wasi-proxy / --wasi-reactor #536

Open
guybedford opened this issue Dec 10, 2024 · 2 comments
Open

jco componentize --wasi-command / --wasi-proxy / --wasi-reactor #536

guybedford opened this issue Dec 10, 2024 · 2 comments

Comments

@guybedford
Copy link
Collaborator

Suggested by @vados-cosmonic it could be useful to have an option for jco componentize to automatically provide a standard WASI world out of the command, proxy and reactor worlds, so that there's no need to configure WITs.

@vados-cosmonic
Copy link
Contributor

Actually suggested by @ricochet , channeled through me into an issue :) should we close the other issue in favor of this one? Or is this more of a shortcut for the general WASI-supported world targeting issue?

@guybedford
Copy link
Collaborator Author

I think that issue is good to track more specifically the wkg tooling wrapping to auto-populate wit data without a local wit folder?

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

No branches or pull requests

2 participants