stackblitz / webcontainer-core

Dev environments. In your web app.
https://webcontainers.io
MIT License
3.93k stars 172 forks source link

DEAD END #1511

Open Murphie1 opened 1 month ago

Murphie1 commented 1 month ago

Describe the bug

I'm trying to create a new Nextjs project with the nextjs starter template and it opens up, boots the WebContainer, and starts installing dependencies with the commands "npm install & npx next dev". Here's the logs in terminal after that: " npm install && npx next dev npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm WARN deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead npm WARN deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead [############......] \ reify:finalize: timing reify:unpack Completed in 499 "

It seems to show the "Completed in (time)" before it finishes loading and after a while my browser returns an error page saying: " Aw Snap! something went wrong while displaying this webpage Error code: RESULT_CODE_KILLED_BAD_MESSAGE "

Link to the blitz that caused the error

https://stackblitz.com/edit/stackblitz-starters-yhz2qk?file=app%2Fpage.tsx

Steps to reproduce

Just open the project and let it load as usual, booting the WebContainer and installing dependencies

Expected behavior

While installing dependencies, the terminal logs should be: " npm install && npx next dev npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm WARN deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead npm WARN deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead [############......] \ reify:finalize: timing reify:unpack Completed in 499 " and then the browser should return an error page saying: " Aw Snap! something went wrong while displaying this webpage Error code: RESULT_CODE_KILLED_BAD_MESSAGE "

Parity with Local

Screenshots

No response

Platform

Browser name  = Chrome
Full version  = 109.0.0.0
Major version = 109
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 44653483,
  "usedJSHeapSize": 40772139,
  "jsHeapSizeLimit": 522190848
}
Hash = e7ca9335

Additional context

No response