-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Use unjs/jiti instead of ts-node #30718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
|
Yah we agree, it's been problematic as noted in #30426 |
We will be replacing |
3 tasks
going to close this issue as it will be resolved with Cypress 15, which is targeted for early July 2025. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like?
Use https://github.com/unjs/jiti instead of ts-node to load
cypress.config.ts
or anything else, if any.Why is this needed?
The last stable release of ts-node was a year ago: https://github.com/TypeStrong/ts-node/releases/tag/v10.9.2
There seems to be a clear maintenance problem, as can be seen here: TypeStrong/ts-node#2077
As can be seen in #30715, #30318, #30101, and others, TypeScript config loading has been problematic, due to the underlying tool, ts-node.
If Cypress switches to a more modern and maintained tool like unjs/jiti or https://github.com/privatenumber/tsx, most (if not all) problems would be solved. Since the tools are still actively being maintained, as opposed to ts-node, it will be more likely to get fixes for newly popping problems due to updated Node or TS specs.
Other
No response
The text was updated successfully, but these errors were encountered: