Steven

@zkochan Thanks, updated 👍

Its hard to know without the source code. Usually this is caused by a dynamic require. You can check in `/Users/seepine/workspace/test-transfer/dist/worker1.js` for something like `require(str)` and change it to `require('./indexes')`...

Regarding json5 vs jsonc, there is a related issue with some discussion about tsconfig.json from a few years ago: - https://github.com/microsoft/vscode/issues/100688

@GeoffreyBooth All of those things can be said of fetch as well, yet I don’t think we should remove fetch from core.

People are [choosing Corepack](https://github.com/search?type=code&q=%22%5C%22packageManager%5C%22%22+path%3Apackage.json) because it shipped with Node.js and because it defines a [canonical way](https://nodejs.org/api/corepack.html) to define your package manager. This is why I chose to add support for...

This would be really nice. I think I would take it a step further so I could also run `remove` or any other subcommand of a given package manager. Maybe...

For more context, I created the original issue https://github.com/nodejs/corepack/issues/354 after the Node.js TSC meeting because some expressed that they didn't like the idea of corepack gatekeeping.

Try with `export COREPACK_ENABLE_STRICT=0`

If I remember correctly, PR https://github.com/nodejs/corepack/pull/413 was implemented at the request of the Node.js TSC after several meetings trying to figure out if corepack should be made stable as part...

Should we just put all the effort into upgrading to 14.1? - https://github.com/nodejs/node/pull/59805 Or is it still valuable to continue trying to upgrade to 13.8 first?