Skip to content

Start Node ESM stable version at Node16 #48879

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

Merged
DanielRosenwasser merged 12 commits into from
May 3, 2022
Merged

Start Node ESM stable version at Node16 #48879

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
c0f2882
Remove Node12, add Node16.
DanielRosenwasser Apr 28, 2022
52d1ea5
Accepted baselines.
DanielRosenwasser Apr 28, 2022
1247217
Refactor checking for top-level await, give a better error message in…
DanielRosenwasser Apr 29, 2022
c390b79
Accepted baselines.
DanielRosenwasser Apr 29, 2022
8b1e656
Stop erroring on JSON module imports in node ESM since they're no lon…
DanielRosenwasser Apr 29, 2022
ce98f0a
Accepted baselines.
DanielRosenwasser Apr 29, 2022
fac5ded
More refactoring, do the same checks for for-await loops.
DanielRosenwasser Apr 29, 2022
5305796
Accepted baselines.
DanielRosenwasser Apr 29, 2022
1ca971d
Adjust phrasing to permit for-await on CJS error.
DanielRosenwasser Apr 29, 2022
4c46f26
Accepted baselines.
DanielRosenwasser Apr 29, 2022
830871c
Accepted baselines.
DanielRosenwasser Apr 29, 2022
9d7fae8
Fix lints.
DanielRosenwasser Apr 29, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Adjust phrasing to permit for-await on CJS error.
  • Loading branch information
@DanielRosenwasser
DanielRosenwasser authored Apr 29, 2022
commit 1ca971df1e98e8b57922c167a4237863dcbbab21
4 changes: 2 additions & 2 deletions src/compiler/checker.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33104,7 +33104,7 @@ namespace ts {
if (sourceFile.impliedNodeFormat === ModuleKind.CommonJS) {
Copy link
Copy Markdown
Member Author

@DanielRosenwasser DanielRosenwasser Apr 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, this check is wrong and the tests reflect that. Should it be

Suggested change
if ((moduleKind !== ModuleKind.ES2022 && moduleKind !== ModuleKind.ESNext && moduleKind !== ModuleKind.System && !(moduleKind >= ModuleKind.Node16 && getSourceFileOfNode(node).impliedNodeFormat === ModuleKind.ESNext)) || languageVersion < ScriptTarget.ES2017) {
if ((moduleKind !== ModuleKind.ES2022 && moduleKind !== ModuleKind.ESNext && moduleKind !== ModuleKind.System && !(moduleKind < ModuleKind.Node16 && getSourceFileOfNode(node).impliedNodeFormat === ModuleKind.ESNext)) || languageVersion < ScriptTarget.ES2017) {

Copy link
Copy Markdown
Member

@weswigham weswigham Apr 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Normally we still emit warnings of some kind when using experimental features, which would still be in all stable versions of node, at least until nodejs/node#42875 ships in the next version of node 18.

Copy link
Copy Markdown
Member Author

@DanielRosenwasser DanielRosenwasser Apr 28, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So maybe until TLA becomes non-experimental we could issue an error like

Top-level 'await' is currently experimental in Node.js. It can only be enabled when the 'module' option is set to 'nodenext'.

Copy link
Copy Markdown
Member

@weswigham weswigham Apr 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On a related note, we should probably remove the experimental warning for json imports in nodenext. Afaik, they've stabilized in node 18. At least the version with the import assertion, anyway. It's contentious among the node maintainers.

Copy link
Copy Markdown
Member Author

@DanielRosenwasser DanielRosenwasser Apr 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR is already merged - that seems like a pretty strong sign that it will be stable, right?

Copy link
Copy Markdown
Member Author

@DanielRosenwasser DanielRosenwasser Apr 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test wasn't wrong, it was just very confusing because the code was in a CJS file. I've updated the check there.

Copy link
Copy Markdown
Member

@weswigham weswigham Apr 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it'll be stable in the next release of node 18, it just hasn't shipped yet, and I don't know if it'll be backported to 16 or not.

Copy link
Copy Markdown
Member

@andrewbranch andrewbranch May 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At what point do they stop backporting features like that? Maintenance LTS? Is it practical to not create a named moduleResolution target until it solidifies?

Copy link
Copy Markdown
Member

@weswigham weswigham May 3, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes are backported to LTS versions unless they're somehow breaking from what I understand, while maintenance LTS versions only get security patches. At least I think that's the general policy. (The definition of "breaking" being the somewhat subjective part)

span ??= getSpanOfTokenAtPosition(sourceFile, node.pos)
diagnostics.add(
createFileDiagnostic(sourceFile, span.start, span.length, Diagnostics.The_current_file_is_a_CommonJS_module_and_cannot_use_await_expressions_at_the_top_level)
createFileDiagnostic(sourceFile, span.start, span.length, Diagnostics.The_current_file_is_a_CommonJS_module_and_cannot_use_await_at_the_top_level)
);
break;
}
Expand Down Expand Up @@ -44196,7 +44196,7 @@ namespace ts {
case ModuleKind.NodeNext:
if (sourceFile.impliedNodeFormat === ModuleKind.CommonJS) {
diagnostics.add(
createDiagnosticForNode(forInOrOfStatement.awaitModifier, Diagnostics.The_current_file_is_a_CommonJS_module_and_cannot_use_await_expressions_at_the_top_level)
createDiagnosticForNode(forInOrOfStatement.awaitModifier, Diagnostics.The_current_file_is_a_CommonJS_module_and_cannot_use_await_at_the_top_level)
);
break;
}
Expand Down
2 changes: 1 addition & 1 deletion src/compiler/diagnosticMessages.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -900,7 +900,7 @@
"category": "Error",
"code": 1308
},
"The current file is a CommonJS module and cannot use 'await' expressions at the top-level.": {
"The current file is a CommonJS module and cannot use 'await' at the top level.": {
"category": "Error",
"code": 1309
},
Expand Down