Using node 18.18.0, which doesn't work with webpack

[NullVoxPopuli]

Describe the bug

Visit: https://stackblitz.com/github/nullVoxPopuli/polaris-starter/tree/webpack

See errors:

[EBADF: bad file descriptor, close] {
  code: 'EBADF',
  errno: -9,
  path: undefined,
  syscall: 'close'
}

Link to the blitz that caused the error

https://stackblitz.com/github/nullVoxPopuli/polaris-starter/tree/webpack

Steps to reproduce

use webpack with node 18.18

this problem: nodejs/node#49911, fixed in 18.18.1

Expected behavior

Node 18.18.1 or newer is used

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• Browser: [e.g. Chrome, Safari, Firefox]
• Version: [e.g. 91.1]

Additional context

No response

[SamVerschueren]

Hey @NullVoxPopuli 👋 . Thanks for reaching out.

I looked into it and it's not because of those issues in Node.js (or at least, the main issue is not). The reason this fails and throws a EBADF error is because a package called thread-loader reads directly from FD 4. The reason you can do this is because if you spawn a new process, you can provide a 5th option to the stdio list which will be exposed as FD 4 as described in the Node.js docs.

Currently this is a limitation of WebContainers and I created an internal ticket to track this.