20 people reported

All time, since Oct 7, including 19 thumbs-up on GitHub.

Page module factory not available

“No chunk that loads for / defines a-page-only or b-boundary.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4111/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Pages Router page modules missing factories in Turbopack dev. Page server-renders, then crashes during hydration because no chunk loading for the page defines some imported modules.

Is this your bug?

File my report
Where
Turbopack dev server
Error text
Module [project]/lib/a-page-only.js [client] (ecmascript) was instantiated because it was required from module [project]/pages/index.js [client] (ecmascript), but the module factory is not available.
Versions
16.4.0
Platforms
macOS
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Build hangs on worker import cycle3 people
  2. Dev server 404s dynamic subroutes2 people
  3. Build spawns a webpack-loader pool per loader chain and context9 people

Original reports1, newest first

  1. Turbopack dev (16.4.0): Pages Router page modules missing ("module factory is not available") after _app availability seeding (#97664)On GitHub#99789

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.