-
Notifications
You must be signed in to change notification settings - Fork 239
WebContainer integration #54
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
Conversation
The issue was that third party cookies were blocked. Will need to add some messaging directing people to allow cookies. On |
This is what happens when a module imports This is what happens when we By the time this fails, the service worker is already registered. Not sure why the request is going to Cloudfront instead of being handled by the worker. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
holy shit it works! https://learn-svelte-n9hbykwwx-svelte.vercel.app/tutorial/welcome-to-svelte I'm going to merge this, then open issues for the remaining TODOs |
Work-in-progress! Closes #2.
This creates a WebContainer, using
@webcontainer/api
, populates its filesystem, installs dependencies and callsnpm run dev
. For some reason theserver-ready
event isn't firing — need to investigate why.Monaco workers are failing to load, probably because of the COOP/COEP headers. Remains to be seen if that will be fatal in production.
Am also seeing this — it's not possible to load
<iframe src="https://github.com/loading.html">
apparently