Thanks for the discussion about "node", some useful links for everyone:

• npm
• DT
• Related discussions

Pinging the DT module owners: @microsoft, @jkomyno, @alvis, @r3nya, @btoueg, @smac89, @Touffy, @DeividasBakanas, @eyqs, @Hannes-Magnusson-CK, @hoo29, @kjin, @ajafff, @islishude, @mwiktorczyk, @mohsen1, @n-e, @galkin, @parambirs, @eps1lon, @ThomasdenH, @WilcoBakker, @wwwy3y3, @samuela, @kuehlein, @bhongy, @chyzwar, @trivikr, @yoursunny, @qwelias, @ExE-Boss, @peterblazejewicz, @addaleax, @victorperin, @ZYSzys, @nodejs, @LinusU, @wafuwafu13, @mcollina, @Semigradsky.

Try to reinstall dependencies.

Same issue started appearing in a release from 3 weeks ago

This definitely seems like a bug with the types, running tsc will yield

../node_modules/@types/node/globals.d.ts:377:25 - error TS2792: Cannot find module 'undici-types'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?

In a project that does not need or use nodenext for modules. (or undici or any other dependencies)

If you are coming across this in your own projects, as a workaround, you can npm i undici-types and then add this to the tsconfig.json

{
  "compilerOptions": {
    "paths": {
      // This is solely to stop a bug with @types/node as of 12/15/2023
      "undici-types": [
        "./node_modules/undici-types/index.d.ts"
      ],
    }
  }
}

And it will work for now.

In my case, the culprit was @types/bun. Once I removed that, no issues.

This is only an issue if you are not using moduleResolution=Node or one of the other Node-specific variants. However, it is quite easy for this to happen even if you are not yourself using @types/node, it is instead installed as part of your development dependencies :-\ In that case setting moduleResolution to Node may not be desirable.

you can npm i undici-types and then add this to the tsconfig.json

This has no effect for me.

Some external libraries may require the use of Commonjs. In such cases, you may encounter problems, and you will need to find alternative solutions .Adding "Moduleresolution": "Node" to your TSCONFIG.JSON file helps the Typescript compiler to determine how to allow modules. This can be useful if you switch your project to use ES6 modules, especially when problems arise with resolving modules and conflicts with various modules systems.

I had the same issue and what resolved it was to create a separate config file for the type script files that were causing it (in my case client.ts):

{ "compilerOptions": { "target": "ES2018", "lib": [ "dom", "es2018" ], "outDir": "./public/js", "module": "none", "skipLibCheck": true }, "files": [ "src/client.ts" ] }

For me, this is causing failure on a basic TypeScript project with no dependencies other than @types/node. Installing undici-types as a dev dependency does not fix the issue.