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

fix: support for "module": "node16"/"nodenext" #24

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

jfirebaugh
Copy link
Contributor

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.

#23

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
@songkeys
Copy link
Owner

There is one test failing. Could you fix it?

should output module:es6 if the nearest package.json is of type:module

I think we should edit the "module" field to "node16" or "nodenext" of tsconfig in fixtures to make this test true.

@songkeys songkeys changed the title Fix support for "module": "node16"/"nodenext" fix: support for "module": "node16"/"nodenext" Oct 16, 2024
@songkeys songkeys merged commit ec3fe9d into songkeys:main Oct 16, 2024
3 of 4 checks passed
@jfirebaugh jfirebaugh deleted the patch-1 branch October 16, 2024 13:07
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

Successfully merging this pull request may close these issues.

2 participants