fix(nextjs): add extension alias support for handling ESM libs #31323
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.
Current Behavior
Currently, if you try to import a ESM lib after you generate a Next.js application it fails to build due to how the module exports
export * from './lib/lib8446520.js';
.This has been addressed with webpack and needs to be extended to Next.js.
Expected Behavior
You should work out of the box and you should be able to import a lib defined like:
export * from './lib/lib8446520.js';.
Related Issue(s)
Fixes #30714