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.

Sign up for GitHub

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

Jump to bottom

Use nodenext compilerOptions.module #4152

Open
wemeetagain opened this issue Jun 13, 2022 · 0 comments
Open

Use nodenext compilerOptions.module #4152

wemeetagain opened this issue Jun 13, 2022 · 0 comments
Assignees
@nazarhussain
Labels
prio-low This is nice to have. scope-none Issues that do not fit within any of the other defined scopes.

Comments

@wemeetagain
Copy link
Member

Since 4.7 supports node16 and nodenext compilerOptions.module option, should we change it? I'm not sure what practical implications does it have to us or if we should use it.

https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/?q=1#esm-nodejs
@wemeetagain wemeetagain mentioned this issue Jun 13, 2022
Merged
@dapplion dapplion added the prio-low This is nice to have. label Jun 29, 2022
@dapplion dapplion added the scope-none Issues that do not fit within any of the other defined scopes. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nazarhussain nazarhussain

Labels
prio-low This is nice to have. scope-none Issues that do not fit within any of the other defined scopes.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nazarhussain @wemeetagain @dapplion