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

[Feature Request] Support tsx and/or custom node commands #76

Open
martaver opened this issue Aug 17, 2024 · 0 comments
Open

[Feature Request] Support tsx and/or custom node commands #76

martaver opened this issue Aug 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@martaver
Copy link

Is your feature request related to a problem? Please describe.

It seems that ts-node is having trouble staying up to date with latest typescript features.

In 5.0, typescript added support for multiple extends syntax in tsconfig.json, and ts-node still doesn't support it, nor does it seem to be active.

As a result, this extension won't run when encountering a tsconfig.json with extends as an array.

Describe the solution you'd like

a) consider defaulting to tsx, swc-node or another more resilient solution.
b) allow customising the command that invokes the debug entrypoint, e.g. instead of <path_to_node>/bin/node --loader=ts-node/esm <entry> allow the user to instead invoke something like <path_to_tsx>/bin/tsx <entry>.

Additional context

Specifically, tsx can be used as a drop-in replacement for node in most commands. Here's how it can be used to debug node processes in vscode: https://tsx.is/vscode

@martaver martaver added the enhancement New feature or request label Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant