-
-
Notifications
You must be signed in to change notification settings - Fork 607
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
esbuild-kit/tsx
loader support for TypeScript configuration
#3905
Comments
Actually this should probably be moved to
|
Yes, we use |
@fregante I think we can provide an option to support loaders that is not supported by |
It seems to me that this already works but I was hoping to see native support since the package is quite popular (more than some existing parsers used by Interpret). However this stopped working in Node 20. See: |
@fregante I think we can send a PR for gulpjs/interpret#95 and ask to merge it, also, yeah, I can modify default loaders array and put this as a temporary workaround until |
Hey everyone, i'm pretty new here and i'd like to work on this issue |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
bum |
If you can require Node.js users to set |
Feature request
What is the expected behavior?
Webpack could use esbuild-kit/tsx automatically if found, just like it already supports:
What is motivation or use case for adding/changing the behavior?
I'd like to use this loader because it's the most straightforward I found so far, without issues and verbose configuration. I wish this was supported natively in Webpack.
How should this be implemented in your opinion?
Is it correct that Webpack uses
interpret
under the hood to load configuration? If so, I think this change can be followed up in its repo:esbuild-kit/tsx
support gulpjs/interpret#95Are you willing to work on this yourself?
Potentially
Also we need:
The text was updated successfully, but these errors were encountered: