PR #1: Improve NoFallbackError message for dynamicParams=false misses

• Repository: michagonzo77/next.js
• Author: michagonzo77
• State: open | merged: False
• Link: https://github.com/michagonzo77/next.js/pull/1

Description (problem / solution / changelog)

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->

What?

• Replaces the internal NoFallbackError message (Internal: NoFallbackError) with a user-facing explanation when a route parameter is rejected because dynamicParams = false.
• Extends test/e2e/app-dir/app-static/app-static.test.ts to assert that next start output no longer includes the internal string and now includes the improved message.

Why?

Issue #87738 reports that the current output is too opaque for users. It exposes an internal control-flow marker instead of explaining the configuration mismatch.

How?

• Updated packages/next/src/shared/lib/no-fallback-error.external.ts message text.
• Added a regression assertion in the existing dynamicParams false e2e test around invalid params.

This fix intentionally keeps scope small (2 files) and does not change routing behavior (still returns 404); it only improves the surfaced message.

Validation

• Ran:
  • NEXT_SKIP_ISOLATE=1 NEXT_TEST_MODE=start pnpm testheadless test/e2e/app-dir/app-static/app-static.test.ts -t "should handle dynamicParams: false correctly"
• Result: passing (1 passed, 110 skipped)
• Before/after proof from captured logs of the same scenario:
  • Before: Error: Internal: NoFallbackError
  • After: Error: A dynamic route parameter was not generated by \generateStaticParams` while `dynamicParams = false`.`

UI / Dev UX proof (before vs after)

<p> [Before: internal NoFallbackError output](https://cursor.com/agents/bc-d0e8ad78-9dd9-4ecd-9532-f6c06bbbf68d/artifacts?path=%2Fopt%2Fcursor%2Fartifacts%2Fscreenshots%2Fbefore-no-fallback-error-message.png) </p> <p> [After: user-facing dynamicParams=false message](https://cursor.com/agents/bc-d0e8ad78-9dd9-4ecd-9532-f6c06bbbf68d/artifacts?path=%2Fopt%2Fcursor%2Fartifacts%2Fscreenshots%2Fafter-no-fallback-error-message.png) </p>

Edge cases / limitations

• The message is generic and intentionally avoids path-specific context.
• Existing code paths that throw NoFallbackError now use this clearer shared message.

Fixes #87738

<!-- NEXT_JS_LLM_PR -->

_{To show artifacts inline, <a href="https://cursor.com/dashboard/cloud-agents#team-pull-requests">enable</a> in settings.}

<!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-d0e8ad78-9dd9-4ecd-9532-f6c06bbbf68d"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-d0e8ad78-9dd9-4ecd-9532-f6c06bbbf68d"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

Changed files

• packages/next/src/shared/lib/no-fallback-error.external.ts (modified, +2/-1)
• test/e2e/app-dir/app-static/app-static.test.ts (modified, +8/-0)

---

PR #92936: NoFallbackError: replace internal-jargon message with actionable guidance

• Repository: vercel/next.js
• Author: yogeshwaran-c
• State: open | merged: False
• Link: https://github.com/vercel/next.js/pull/92936

Description (problem / solution / changelog)

What?

Replace the NoFallbackError message from the unhelpful "Internal: NoFallbackError" with one that names the most common cause and links to the relevant docs.

Why?

NoFallbackError is an internal control-flow signal — the framework normally catches it and turns it into a 404 response, so the message is rarely seen by end users. But when it does leak to a server log (as reproduced in #87738 — a parent app router segment with dynamicParams: false plus a request whose params aren't in generateStaticParams()), the user sees:

``` Error: Internal: NoFallbackError at <anonymous> (.next/server/chunks/ssr/babdf1ac..js:2:1128) ... ```

…which gives them no idea what went wrong, what to look for in their app, or where to read more. They have to chase it through Next.js source code to figure out the connection to dynamicParams.

How?

Replace the static message with one that names the common cause and links to the route segment config docs:

``` No fallback was rendered for this route, so the request returned a 404. A common cause is dynamicParams: false on a parent segment combined with a request whose params were not returned by generateStaticParams(). See https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamicparams ```

Also switched from super(); this.message = ... (the old form) to the conventional super(message).

The error message is the only public surface of the class — no behavior change for the framework's normal catch-and-handle flow. Every instanceof NoFallbackError check in base-server.ts, next-server.ts, router-server.ts, etc., still works exactly as before.

Scope

Just the message. The PR deliberately does not try to enrich NoFallbackError with per-call context (which segment / route / params triggered it). That would require plumbing through every throw site (see grep for new NoFallbackError() in app-page.ts, app-route.ts, pages-handler.ts) and is a separate, larger change. The static message is already a substantial improvement on the no-info-at-all status quo.

Test plan

Added test/unit/no-fallback-error.test.ts with two cases:

• The class is an Error subclass (sanity check).
• The message contains dynamicParams, generateStaticParams, and a nextjs.org/docs/ URL — locks in the actionable wording so a future edit can't silently regress to "Internal: NoFallbackError".

npx jest test/unit/no-fallback-error.test.ts → 2 passed.

Fixes #87738

Changed files

• packages/next/src/shared/lib/no-fallback-error.external.ts (modified, +18/-2)
• test/unit/no-fallback-error.test.ts (added, +18/-0)