Sourcemaps point to wrong line number in Cypress in TypeScript version 5

[jennifer-shehane]

Current behavior

Sourcemaps point to the wrong line number in some version of TS 5.

*Note: There were some earlier reports of the stack trace not displaying at all in an error, but this was never reproducible.

Desired behavior

In order to get sourcemaps to work we have to do some monkeypatching to force the sourcemap options to generate them the way we expect. There's likely something that's changed in some version of TS 5 here.

Test code to reproduce

TS code - don't have repro

Cypress Version

13.6.1

Node version

18

Operating System

Mac

Debug Logs

No response

Other

No response

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[TimVee]

The line numbers of assertions errors in run mode are still incorrect.

[ryanthemanuel]

@TimVee or anyone else following this issue, I've been spending some time looking into this and I'm not able to reproduce this with a couple of scenarios I've tried. Do you have a minimal example of this failing for you that I can take a look at?

[TimVee]

I could reproduce it easily:

1. Created a new project
2. pnpm init
3. pnpm add cypress typescript
4. npx cypress open
5. Let Cypress scaffold the example test cases
6. Added tsconfig.json

   {
     "compilerOptions": {
       "target": "ES2018",
       "lib": ["ES2018"],
       "types": [],
       "moduleResolution": "node"
     },
     "include": ["**/*.ts"]
   }

7. Renamed cypress/e2e/1-getting-started/todo.cy.js to .ts
8. Added an error in the test.
9. Ran the test

I added the error on line 24, but in the Cypress test runner that becomes line 21:

[jennifer-shehane]

@TimVee This issue seems different from the original issue - which is that NO stack trace is available for viewing in the error. I do see this being a problem though, that the lines are off sometimes. I think we'll update this issue to track that since the other situation hasn't been demonstrated.