Radpack fails when requiring/importing node built-in module

[jared-smith-kr]

We're experimenting with using radpack with rollup for module federation in in a node.js application and we're having problems when requiring/importing node.js built-in modules, in particular worker_threads:

import { isMainThread, parentPort, Worker } from 'worker_threads'
// error! unknown export 'worker_threads'

The traceback points at this line of code in radpack rollup plugin which as far as I can read is choking because it can't find the index for that package in the registry map.

Did we do something wrong or is there a way to tell the process to defer resolution of that package to runtime or something else that would solve this?

[trhinehart-godaddy]

This is somewhat by design, as by default radpack libraries built with the rollup plugin are meant to be universal (work on the client and sever). As a workaround, try using @rollup/plugin-node-resolve with preferBuiltins as true and use rollup-plugin-external-globals with a configuration to use the available global.require that will bypass rollup's default behavior.

{
  plugins: [
    nodeResolve({ preferBuiltins: true }),
    externalGlobals({
      'worker_threads': `(global.require(${ JSON.stringify('worker_threads') }))`
    })
  ]
}

[jared-smith-kr]

That seems to be working. Thanks for the quick response!