-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
REPL import statement support #213
Comments
tsx is not interested in Deno compatibility. tsx is interested in adding TypeScript support in Node, but this has nothing to do with it. While I agree this would be a nice feature, this should be a feature request for Node.js. |
I'm not sure if alignment with ts-node is at all desired, but this is something that it supports with the right configuration. |
Why dont you open a feature request with Node? |
@privatenumber Just sharing some context. No need to get upset at me. |
Im not upset. Genuine question. I really think this feature request should be filed with Node since it's an obvious DX improvement. |
I did already filed with Node. But think in another way, tsx do AST transform, while node consider not. So, maybe easier to implement such feature during AST transform. |
That's cool, thanks for sharing! However, tsx is a TypeScript & ESM enhancement, and not a place to just add arbitrary Node improvements. I would keep pushing it in Node as that's where it belongs. Try tagging stake holders and get more people involved. Alternatively, you can start a separate project to enhance Node. |
Feature request
REPL import statement support
Why?
Alternatives
Rewrite
To
Additional context
#52
The text was updated successfully, but these errors were encountered: