-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support "module": "node16"/"nodenext"
#23
Comments
Thank you for bringing up this issue. It has been fixed and released in version |
Well, now
|
Thank you! |
jfirebaugh
added a commit
to jfirebaugh/tsconfig-to-swcconfig
that referenced
this issue
Oct 15, 2024
With `"module": "node16"` and `"module": "nodenext"`, look at package.json to determine whether module type is es6 or commonjs. Previously, these values would unconditionally be treated as es6. songkeys#23
Sure, thanks for the encouragement: #24 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, tsconfig-to-swcconfig always outputs
"module": { "type": "commonjs" }
when the input tsconfig uses"module": "node16"
or"module": "nodenext"
. Instead, if the nearestpackage.json
has"type": "module"
, it should output"module": { "type": "es6" }
.The text was updated successfully, but these errors were encountered: