gatsbyjs/gatsby · error · Error

page resources for ${browserLoc.pathname} not found. Not ren

Error message

page resources for ${browserLoc.pathname} not found. Not rendering React

What it means

production-app render loop: the page resources lookup returned no page or a PageResourceStatus.Error result, so React rendering is skipped. If the chunk itself errored, the underlying page.error is rethrown to preserve the real cause; otherwise the generic message is thrown.

Source

Thrown at packages/gatsby/cache-dir/production-app.js:256

        }
      }
    }

    if (sessionStorage) {
      sessionStorage.removeItem(reloadStorageKey)
    }

    if (!page || page.status === PageResourceStatus.Error) {
      const message = `page resources for ${browserLoc.pathname} not found. Not rendering React`

      // if the chunk throws an error we want to capture the real error
      // This should help with https://github.com/gatsbyjs/gatsby/issues/19618
      if (page && page.error) {
        console.error(message)
        throw page.error
      }

      throw new Error(message)
    }

    const SiteRoot = apiRunner(
      `wrapRootElement`,
      { element: <LocationHandler /> },
      <LocationHandler />,
      ({ result }) => {
        return { element: result }
      }
    ).pop()

    const App = function App() {
      const onClientEntryRanRef = React.useRef(false)

      React.useEffect(() => {
        if (!onClientEntryRanRef.current) {
          onClientEntryRanRef.current = true
          if (performance.mark) {

View on GitHub (pinned to e85d62f177)

Solutions

  1. Run a full production rebuild to regenerate page-data and chunks
  2. Check the build output for failed page queries
  3. Verify the route/path exists and matches a created page
Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at packages/gatsby/cache-dir/production-app.js:256 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26). Data as JSON: /api/errors/9159ad7360ea1dda. Report an issue: GitHub.