Build modern CommonJS and support package.json exports #336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
node16for building CJSWarning
Unless
moduleResolutionis explicitly set toclassic,nodeornode10- thencommonjs(Node <v12 style CJS) will be used.Output leaves dynamic
import()calls as-is, so CommonJS can asynchronously import ESM (Node can import ESM from CJS).TypeScript documentation
Node.js v12 security support reached EOL in 2022 (and active support in 2020).
Use
node16ornodenextores2022for building ESMIf the nearest tsconfig.json's
moduleResolutionis eithernode16ornodenext, themodulewill use that value. Otherwise, it'll usees2022.Aside from building to "modern" CJS, another benefit of using
module: node16is that it works withmoduleResolution: node16 | nodenext(allowing the usage ofexportsfield in package.json) whereasmodule: commonjsdoesn't.