Typescript 4.7 with new moduleResolution mode node16/nodenext does not resolve types

Current behavior

Types are not correctly resolved when using typescript 4.7 with moduleResolution set to “node16”.

https://www.typescriptlang.org/docs/handbook/module-resolution.html

error TS2688: Cannot find type definition file for ‘cypress’.

Desired behavior

Types should be resolved.

Test code to reproduce

{
  "compilerOptions": {
    "target": "ES2022",
    "lib": ["ES2022"],
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "node16",
    "moduleResolution": "node16",
    "allowJs": true,
    "resolveJsonModule": true,
    "isolatedModules": true,
    "esModuleInterop": true,
    "types": ["node", "cypress"]
  }
}

Cypress Version

10.1.0

Other

I believe this being due to new module resolution logic requiring explicit extension. Currently the package.json types field just says types (referring to the folder where historically it would’ve been inferred to use index.d.ts) but now needs to be explicit and configured as types/index.d.ts

[smmccabe]

I get the same problem, but the above fix doesn’t work. Also this isn’t a problem with cypress v9, just with cypress v10, at least for me. I’ve been using nodenext since typescript 4.5 as experimental and it has always worked fine with cypress up until now.

[louisscruz]

I think the blast radius of this issue might be larger than described here. I’m seeing the type issues mentioned above in TypeScript 4.5.2 in a Yarn PnP project. After “unplugging” and applying the fix from https://github.com/cypress-io/cypress/pull/22498, the issue goes away.