Problems with Next and internal libs #30714

gperdomor · 2025-04-14T15:50:11Z

Current Behavior

You can't use internal workspace libs in your next apps... The packages are not resolved

Expected Behavior

The apps should works as expected...

GitHub Repo

https://github.com/gperdomor/nx-next-issue

Steps to Reproduce

Create an empty workspace
Create a sample js library
Create a next app
Use the library inside your next app
Run the app and open a page... Is working as expected
~~Update next to latest 15.3.0 version (also in package.json from the app folder)~~
~~Run the app again and open a page... Make sure that runs with next 15.3.0, if not please remove .next folder and node_modules inside your app folder.~~
You will get something like this:

Nx Report

nx report

 NX   Report complete - copy this into the issue template

Node           : 22.14.0
OS             : darwin-x64
Native Target  : x86_64-macos
npm            : 11.3.0

nx (global)            : 20.8.0
nx                     : 20.8.0
@nx/js                 : 20.8.0
@nx/eslint             : 20.8.0
@nx/workspace          : 20.8.0
@nx/devkit             : 20.8.0
@nx/eslint-plugin      : 20.8.0
@nx/module-federation  : 20.8.0
@nx/next               : 20.8.0
@nx/react              : 20.8.0
@nx/vite               : 20.8.0
@nx/web                : 20.8.0
@nx/webpack            : 20.8.0
typescript             : 5.7.3
---------------------------------------
Registered Plugins:
@nx/js/typescript
@nx/vite/plugin
@nx/eslint/plugin
@nx/next/plugin
---------------------------------------
Cache Usage: 0.00 B / 93.15 GB

Failure Logs

nx run website:dev --turbo

> next dev --turbo

   ▲ Next.js 15.3.0 (Turbopack)
   - Local:        http://localhost:3000
   - Network:      http://192.168.1.93:3000

 ✓ Starting...
 ✓ Ready in 2s
 ○ Compiling / ...
 ✓ Compiled / in 1082ms
 ⨯ ./packages/sample-lib/src/index.ts:1:1
Module not found: Can't resolve './lib/sample-lib.js'
> 1 | export * from './lib/sample-lib.js';
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  2 |



https://nextjs.org/docs/messages/module-not-found



./apps/website/src/app/page.tsx:1:1
Export sampleLib doesn't exist in target module
> 1 | import { sampleLib } from '@sandbox/sample-lib';
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  2 | import styles from './page.module.css';
  3 |
  4 | export default function Index() {

The export sampleLib was not found in module [project]/packages/sample-lib/src/index.ts [app-rsc] (ecmascript) <exports>.
The module has no exports at all.
All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist.


 ○ Compiling /_error ...
 ✓ Compiled /_error in 1073ms
 GET / 500 in 2421ms

n^C

—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target dev for project website

Package Manager Version

npm 11.3.0

Operating System

macOS
Linux
Windows
Other (Please specify)

Additional Information

No response

ianldgs · 2025-04-15T13:59:22Z

Out of curiosity: have you tried rspack?

https://github.com/vercel/next.js/blob/canary/examples/with-rspack/next.config.js

mj-meyer · 2025-04-19T15:00:24Z

can confirm, I'm running into the same issue

gperdomor · 2025-04-23T15:43:41Z

Any update or workaround for this? 👀

gperdomor · 2025-05-23T01:59:11Z

@mj-meyer did you find a solution for this?...

gperdomor · 2025-05-23T02:17:40Z

Hi @ndcunningham, did you was able to take a look at this?... At the end also occurs in Next 15.2 too, not in Next 15.3 :(

ndcunningham · 2025-05-23T23:50:38Z

Hey, I took a look and the problem here is Next.js by default doesn't support esm libs extensions import as .js.

A workaround is to just change your library export from .js to .ts and it should work.
Additionally, you can configure your next.config.js to resolve the .js extension to also be .ts.

const nextConfig = {
  webpack: (config) => {
    config.resolve.extensionAlias = {
      '.js': ['.js', '.ts', '.tsx'],
    };
    return config;
  },
  nx: {
    // Set this to true if you would like to use SVGR
    // See: https://github.com/gregberge/svgr
    svgr: false,
  },
};

A fix is coming shortly!

closes: #30714

gperdomor · 2025-05-24T03:31:20Z

@ndcunningham there is something else happening...

If you create a lib, publish the package, and install the package in a new next app in another Nx workspace or created with npx create-next-app, is not working...

The problem is the "development": "./src/index.ts", line inside the package.json exports...

Removing that line make the library works in external next apps

ndcunningham · 2025-05-24T19:02:21Z

@gperdomor can you create a new issue for this so that it can be tracked?
Be sure to include the reproduction steps as well thanks!

gperdomor · 2025-05-25T20:55:02Z

@ndcunningham this is the new issue #31332 to track the new cases, let me know if you need something else 🙏🏻

ndcunningham · 2025-05-27T16:50:49Z

After looking further into this I think there are two issues related to both Webpack and Turbopack.
The webpack issue will be fixed with the PR but serving using turbopack --turbo still does not work.

I think that this issue is related to turbopack as the configuration should be the same as webpack.
I found a few issues on Vercel's github here is one: vercel/next.js#69426 (comment)

closes: #30714

## 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)  This is also related to our webpack and rspack packages. Changes have also been made to them to ensure consistency across bundlers. Fixes #30714

## 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)  This is also related to our webpack and rspack packages. Changes have also been made to them to ensure consistency across bundlers. Fixes #30714 (cherry picked from commit ae89efb)

gperdomor added the type: bug label Apr 14, 2025

FrozenPandaz assigned ndcunningham Apr 14, 2025

FrozenPandaz added scope: nextjs Issues related to NextJS support for Nx priority: medium Medium Priority (not high, not low priority) labels Apr 14, 2025

This was referenced Apr 17, 2025

Where to put @nx/plugin #30768

Open

Running Plugins in an ESM Repo #30744

Open

gperdomor changed the title ~~Problems witn next 15.3 and internal libs~~ Problems with next and internal libs May 23, 2025

gperdomor changed the title ~~Problems with next and internal libs~~ Problems with Next and internal libs May 23, 2025

ndcunningham added a commit that referenced this issue May 23, 2025

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

5f5760d

closes: #30714

ndcunningham mentioned this issue May 23, 2025

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

Merged

gperdomor mentioned this issue May 25, 2025

[@nx/js] Published libs are not working #31332

Open

4 tasks

ndcunningham added a commit that referenced this issue Jun 5, 2025

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

b0f3f08

closes: #30714

ndcunningham closed this as completed in #31323 Jun 5, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Problems with Next and internal libs #30714

Problems with Next and internal libs #30714

gperdomor commented Apr 14, 2025 •

edited

Loading

ianldgs commented Apr 15, 2025

Uh oh!

mj-meyer commented Apr 19, 2025

Uh oh!

gperdomor commented Apr 23, 2025

Uh oh!

gperdomor commented May 23, 2025

Uh oh!

gperdomor commented May 23, 2025

Uh oh!

ndcunningham commented May 23, 2025 •

edited

Loading

Uh oh!

gperdomor commented May 24, 2025

Uh oh!

ndcunningham commented May 24, 2025 •

edited

Loading

Uh oh!

gperdomor commented May 25, 2025 •

edited

Loading

Uh oh!

ndcunningham commented May 27, 2025

Uh oh!

Problems with Next and internal libs #30714

Problems with Next and internal libs #30714

Comments

gperdomor commented Apr 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Current Behavior

Expected Behavior

GitHub Repo

Steps to Reproduce

Nx Report

Failure Logs

Package Manager Version

Operating System

Additional Information

ianldgs commented Apr 15, 2025

Uh oh!

mj-meyer commented Apr 19, 2025

Uh oh!

gperdomor commented Apr 23, 2025

Uh oh!

gperdomor commented May 23, 2025

Uh oh!

gperdomor commented May 23, 2025

Uh oh!

ndcunningham commented May 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gperdomor commented May 24, 2025

Uh oh!

ndcunningham commented May 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gperdomor commented May 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ndcunningham commented May 27, 2025

Uh oh!

gperdomor commented Apr 14, 2025 •

edited

Loading

ndcunningham commented May 23, 2025 •

edited

Loading

ndcunningham commented May 24, 2025 •

edited

Loading

gperdomor commented May 25, 2025 •

edited

Loading