Panics while calling twice

[satouriko]

thread '<unnamed>' panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/napi-3.0.0/src/error.rs:451:1:
assertion `left == right` failed: Check exception status failed
  left: 1
 right: 0
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error [RuntimeError]: unreachable]

https://stackblitz.com/edit/stackblitz-starters-sxccn3md

[Boshen]

❯ node index.js
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done
 
dependencies:
+ @oxc-resolver/binding-wasm32-wasi 11.6.0

Done in 8.7s
[napi-postinstall@0.3.2] Downloading `@oxc-resolver/binding-wasm32-wasi@11.6.0` on WebContainer...
(node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
foobar.js
foobar
entry2.js
foobar2

Cannot reproduce.

[satouriko]

I stably reproduce it every time. 😳

[Boshen]

Fixed in v11.6.1/

TypeError [Error]: The "node:internal/modules/esm/resolve 'resolve' hook's nextResolve() specifier" argument must be of type string. Received undefined

[satouriko]

I still reproduce this error, updated to 11.6.1
https://stackblitz.com/edit/stackblitz-starters-sxccn3md
You don't see the same error output from the stackblitz terminal?

[satouriko]

If you don't see the error for the first time after the web container boots, run it again and you might be able to see it.

[Boshen]

I failed to find the root cause of this problem, and yet to come up with a work around. There must be something fundamentally broken on stackblitz, probably related to memory issues.