History

Nicholas Cunningham ae89efb8d1

fix(nextjs): add extension alias support for handling ESM libs (#31323 )

<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->
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
<!-- This is the behavior we should expect with the changes in this PR
-->

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)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
This is also related to our webpack and rspack packages. Changes have
also been made to them to ensure consistency across bundlers.

Fixes #30714

2025-06-05 13:54:29 -06:00

docs

feat(misc): handle artifact generators' path options including file extensions (#29111 )

2024-12-09 09:13:15 -05:00

plugins

fix(nextjs): add extension alias support for handling ESM libs (#31323 )

2025-06-05 13:54:29 -06:00

src

fix(nextjs): Update glob for cache output (#31177 )

2025-05-12 16:42:07 -04:00

typings

fix(nextjs): use next.js image types (#6556 )