-
Notifications
You must be signed in to change notification settings - Fork 171
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
Open-sourcing for the webplatform ? #458
Comments
short answer: not really longer answer ... webcontainer is a compatibility layer for node apps, similar to wine (Wine Is Not an Emulator)
so were looking for a compatibility layer between node.js apis and web apis some node apis have polyfills, see https://github.com/niksy/node-stdlib-browser
fs has some mocks, see https://github.com/niksy/node-stdlib-browser#mocking-fs child_process
related
closed source
|
We don't have any immediate plans to open source WebContainers, beyond the API client library in @webcontainer/api. This might or might not change in the future, but I'm closing this issue for now, as it's not really actionable/trackable. If/when that happened, I'm pretty sure that we would make a lot of noise in https://blog.stackblitz.com/ and other venues. Thanks for the suggestion! |
@jrvidal any plans yet? offline-first would be perfect for my needs |
just for educational purposes |
This is super cool, I'll take a look |
Is your feature request related to a problem? Please describe:
It would be great if any website could have its own "WebOS" and be able to launch their own "Web Containers" in order to have offline-first backend applications directly working into the browser.
Describe the solution you'd like:
Is there any plan on open-sourcing the technology or to begin a standardization process which would allow more actors in the industry to participate to a collective project ?
Describe alternatives you've considered:
Would deno be a better choice than node.js as a wasm component (as deno is built in Rust which is directly compilable to wasm and has a nodejs compatibility layer) ?
Additional context:
The idea of
Trusted Desktop Activity
has been suggested since november 2018 in the chromium repo.Some similar ideas from the issue in chromium repo:
The text was updated successfully, but these errors were encountered: