`--conditions xxx` cannot pass into `worker_thread`

[himself65]

Version

v20.10.0

Platform

Darwin Alexs-MacBook-Pro.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020 arm64

Subsystem

module

What steps will reproduce the bug?

// main.js
import { Worker } from 'node:worker_threads'

new Worker(new URL('worker.js', import.meta.url), {
  execArgv: ['--conditions', 'react-server']
})

// worker.js
import { register } from 'node:module'

register('./register.js', import.meta.url)

console.log('1')

import('./test.js')

// register.js
export async function resolve (specifier, context, nextResolve) {
  // Take an `import` or `require` specifier and resolve it to a URL.
  console.log('context', context.conditions)
  return nextResolve(specifier, context, nextResolve)
}

export async function load (url, context, nextLoad) {
  return nextLoad(url, context, nextLoad)
}

// test.js
console.log('3')

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

1
context [ 'node', 'import', 'node-addons', 'react-server' ]
3

What do you see instead?

1
context [ 'node', 'import', 'node-addons' ]
3

Additional information

Might cause RSC bundle issue https://github.com/dai-shi/waku/pull/178

[juanarbol]

I think I can work on this one <3

Thanks for the report

[himself65]

I think I can work on this one <3

Thanks for the report

Appreciate it

[juanarbol]

For whatever reason, Node.js is creating three workers, the first one is receiving and setting the context, as expected, but the next two are not, I'm still working on it

[juanarbol]

Oh yes, the loader now lives on a worker thread; I'll see how I could send the argv to those workers.

[GeoffreyBooth]

@nodejs/loaders

[himself65]

I believe that the bug is more complex than I thought

[himself65]

https://github.com/himself65/node-js-worker-thread-hook