Skip to content
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

Use a different script runner than ts-node for better performance #44

Open
PatrickLehnerXI opened this issue Nov 19, 2021 · 1 comment

Comments

@PatrickLehnerXI
Copy link
Contributor

Would it be possible to use a different script runner than ts-node? Especially for short build scripts, ts-node is quite slow -- and I don't need to type-check my build scripts all the time. In our TS code base, we're using babel-node as our runner, which only transpiles and is therefore significantly faster.
Additionally, we recently found out that ts-node can be configured to use swc for transpilation. If this works for devcmd, this issue might be solvable by configuration.

Note: This feedback was provided internally at XITASO, so I'm creating this issue for tracking.

@PatrickLehnerXI PatrickLehnerXI changed the title Use a different script runner than ts-node Use a different script runner than ts-node for better performance Nov 19, 2021
@PatrickLehnerXI
Copy link
Contributor Author

Another XITASO colleague added to this:

ts-node also has a command-line option -T that enables transpile-only mode, I have sometimes wished this could be used. However, in that case I'm not sure how the scripts would still be type-checked.

This could be a possible (temporary) quick-fix while we consider replacing the script runner permanently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant