Skip to content

Conversation

@ybiquitous
Copy link
Member

Which issue, if any, is this issue related to?

None.

Is there anything in the PR that needs further explanation?

The source files have already been .mjs and ESM-compatible. This change should not affect the runtime behavior.

The source files have already been `.mjs` and ESM-compatible.
This change should not affect the runtime behavior.
@ybiquitous ybiquitous requested a review from a team as a code owner December 3, 2025 02:01
@@ -1,8 +1,7 @@
{
"compilerOptions": {
"target": "ES2019",
Copy link
Member Author

Choose a reason for hiding this comment

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

[note] If module is NodeNext, then target is set to ESNext by default.

Ref https://www.typescriptlang.org/tsconfig/#target

"module": "commonjs",
"lib": ["ES2019"],
"module": "NodeNext",
"lib": ["ESNext"],
Copy link
Member Author

Choose a reason for hiding this comment

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

[note] As long as there are no problems, we should keep ESNext, regardless of supported Node.js versions.

Ref:

"engines": {
"node": ">=20.19.0"
}

Copy link
Member

@jeddy3 jeddy3 left a comment

Choose a reason for hiding this comment

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

LGTM, thank you.

@ybiquitous ybiquitous merged commit aa0d603 into main Dec 3, 2025
14 checks passed
@ybiquitous ybiquitous deleted the migrate-to-esm branch December 3, 2025 10:02
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.

3 participants