-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[💡 Feature]: Replace ts-node
with tsx
#11878
Comments
Thanks for reporting! We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers! |
Now I solved this with running Config need to be compiled to JS or need to be written in plain JS in case to prevent loading ts-node in @wdio/config by detection of extention of config file |
@Delagen writing the config to the file system as JS file is not an option. We should provide the ability to just load TS files and execute them. |
@christian-bromann I understand, I use config in JS only to prevent loading of ts-node. All tests and etc. written in Typescript, an d not transpiled to JS manually, all compilation in memory via TSX Only problem now, is ts-node if it present in node_modules it still try to load by runner, so I have to remove it manually with editing package.lock.json to enable execution in CI. |
I took a look at this but it seems there is a fair bit of overlap with the removal of transpiler choice / Some things I noted:
|
Sounds good to me. I am open to remove |
@goosewobbler sounds good. I think it is good to stick as much as possible to how the tools work out of the box (no config using wdio but instead document how wdio can be used with tsx). So if tsx recommends using environment variables to appoint a tsconfig then we just point to the tsx documentation, simple, clean and most of all less maintenance and confusion |
@erwinheitzman |
I think being able to provide the path to a |
Re-assigning this to @goosewobbler as he took a first stab at a PR on this. |
Is your feature request related to a problem?
We have been running into issues using
ts-node
lately, see:For running TypeScript files on demand we currently use
ts-node
which seems to have difficulties with ESM/CJS as well as sourcemaps.Describe the solution you'd like.
Switch to
tsx
which seems to have general better support for it.Describe alternatives you've considered.
n/a
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: