[Bug]: Page keep re-rendering after any change during development

[juffalow]

Reproduction

export default function Page() {
  const promise = loadData();

  return (
    <ErrorBoundary>
      <Suspense fallback={<Loader />}>
        <Detail promise={promise} />
      </Suspense>
    </ErrorBoundary>
  );
}

The actual project is here.

System Info

System:
    OS: macOS 15.0.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 689.23 MB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.16.0 - ~/.nvm/versions/node/v22.16.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.16.0/bin/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm
    pnpm: 10.17.1 - ~/.nvm/versions/node/v22.16.0/bin/pnpm
  Browsers:
    Chrome: 140.0.7339.214
    Safari: 18.0.1

Used Package Manager

npm

Expected Behavior

On any code change, the app hot-reloads / re-renders.

Actual Behavior

On any code change, the app keeps re-rendering in an infinite loop.

[rururux]

Is that Promise memoized?
For example, using useMemo or similar.

[juffalow]

I tried it and it did not help. Still re-rendering.

[juffalow]

What helps is to not create the promise directly in the component, but init it in a useEffect.

[rururux]

Is that problem occurring on this page / file?
https://github.com/juffalow/zdielaj-si/blob/master/application/app/routes/album.tsx

[rururux]

I tried creating a minimal reproduction, but I couldn't reproduce the issue.
https://stackblitz.com/edit/github-aht5tmru?file=app%2Froutes%2Fpokemon.tsx

[github-actions]

To align with our new Open Governance model, we are now requiring that all issues have a minimal and runnable reproduction. This should help us to focus on actionable issues and be more responsive to newly filed issues.

To get this re-opened, please add a reproduction to the Issue description and tag @brophdawg11 or @brookslybrand in a comment so we can re-open.

Or, if this was closed by mistake and there is a valid reproduction, please ensure that it is linked in the Issue description and and tag @brophdawg11 or @brookslybrand in a comment so we can re-open.

If you have any questions, you can always reach out on Discord. Thanks again for providing feedback and helping us make React Router even better!

[brophdawg11]

Would you mind recreating this issue in a smaller reproduction? Per the bug template:

Please note that all bugs must have a minimal and runnable reproduction, meaning that it is not just pointing to a deployed site or a branch in your existing application, or showing a small code snippet. For more information, please refer to the Bug/Issue Process Guidelines.

That way we can rule out this being an issue stemming from something specific elsehwere in your application.