-
Notifications
You must be signed in to change notification settings - Fork 176
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
Unable to tearDown and ReBoot webcontainer on page change #1178
Comments
hi 👋 thanks for reporting this issue! I pulled the code and started the app, but wasn't sure exactly how the error should be trigger. Can you list the steps you take to reproduce this issue? |
if you run it locally then it shows the four routes when i switch to /playground it boots webcontainer successfully and when user gets back again /playground then it shows error webcontainer already booted! |
@kirjavascript no reply since 2 days |
Thanks for the reproduction notes, We've been trying to debug this issue but haven't got to the bottom of it yet. Once the issue if figured out we will post an update here! |
any updates @kirjavascript ? |
Describe the bug
GITHUB LINK: https://github.com/pratham15541/webcontainer-trial-react
i am trying to teardown webcontainer and once again boot in react app
but it shows error:
/docs
Webcontainer.jsx:98 null
Webcontainer.jsx:59 Booting WebContainer...
Webcontainer.jsx:75 WebContainer booted successfully!
/docs
Webcontainer.jsx:98 {"_instance":{},"_runtimeInfo":{"path":"/bin:/usr/bin:/usr/local/bin","cwd":"/home/httplocalhost5173-b5wu"},"_iframe":{},"fs":{"_fs":{}}}
Webcontainer.jsx:101 Stopping WebContainer...
Webcontainer.jsx:104 WebContainer stopped
Webcontainer.jsx:59 Booting WebContainer...
Webcontainer.jsx:93
Error booting WebContainer: Error: WebContainer already booted
at WebContainer.boot (index.js:140:19)
at initializeComponents (Webcontainer.jsx:60:47)
at Webcontainer.jsx:150:7
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/pratham15541/webcontainer-trial-react
Steps to reproduce
code:
Expected behavior
i think it should destroy and again start new webcontainer Instance..
Parity with Local
Screenshots
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: