Cypress forces an invalid moduleResolution value for Typescript 5.7.3; it is unable to start

[stevematney]

Current behavior

Because of the forced moduleResolution value in #28709, Typescript 5.7.3 fails saying that "node" is not a valid "moduleResolution" value. (It was deprecated: moduleResolution docs).

The specific text of the failure is:

Error: Debug Failure. Unexpected moduleResolution: node

Note: this seems to only happen when a project is freshly updated to cypress@14 and [email protected]. It seems to be, if Cypress has been run successfully on a previous TS version, it continues working. (This may not be precisely correct, as the exact conditions of the failure have been difficult to pin down.)

Desired behavior

Cypress should default to a current, valid moduleResolution value

Test code to reproduce

This should be reproducible by simply updating any Cypress project using typescript to using [email protected]

Cypress Version

14.0.0

Node version

v22.13.0

Operating System

macOS 15.2

Debug Logs

Other

No response

[jennifer-shehane]

@stevematney Where are you seeing the error exactly? What were the steps you did after setting these versions?

[stevematney]

@stevematney Where are you seeing the error exactly? What were the steps you did after setting these versions?

Hi @jennifer-shehane! I updated a project from cypress@13 to cypress@14, and updated from [email protected] to [email protected].

I think this has something to do with my module and moduleResolution settings in the tsconfig, and how cypress modifies that at runtime. I'm using "module": "esnext" and "moduleResolution": "bundler". It seems a bit difficult to reproduce locally because, after I have successfully run it once, it continues to work, even after I update my tsconfig values to something that may not have worked before—so likely something that Cypress puts on disk allows it to continue functioning—but when I try to run the same thing in CI, it fails with the above error.

[jennifer-shehane]

@stevematney After upgrading the versions, you're running cypress run or cypress open? Where are the errors displaying?

[stevematney]

After upgrading the versions, you're running cypress run or cypress open? Where are the errors displaying?

The errors display in both cases. They display on cypress open if the cypress version is a fresh install on the machine. They display on cypress run in CI.

[stevematney]

Just one more note: I found that running cypress cache clear gets me to the point where I can reproduce this locally, as well.

[AtofStryker]

Hi @stevematney. I am trying to reproduce this issue in https://github.com/AtofStryker/cypress-issue-30954 but am unable to reproduce. I have tried clearing the cache as well and using the tsconfig values you have provided in the issue. Would you be able to guide me in reproducing the issue in that github repository or helping me fill in the blanks?

[stevematney]

@AtofStryker I can try to take a look at your reproduction repo soon! I'm not actually sure the precise config that is needed to get it to happen, but it is currently reproducible every time in this repo on the main branch:
https://github.com/WTW-IM/es-components/actions/runs/13017167681/job/36309109594#step:7:27