not rendered Suspense fallback when change route

[d0hyeon]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

react: >= 18
next: >= 12.1.0

Which example does this report relate to?

all

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

not rendered Suspense fallback when change route

function Component () {
  const { query: { page } } = useRouter();
  const { data } = useQuery([page], () => api.get('...', { params: { page } }) );

  return (
    <p>{data}</p>
  )
}

function App () {
  return (
    <Suspense fallback="loading...">
      <Component /> 
    </Suspense>
  )
}

I think it's because of the startTransition of react
https://github.com/vercel/next.js/blob/canary/packages/next/src/client/index.tsx#L518-L522

Expected Behavior

render fallback component

can i perform this when provide startTransition option like priority of next/image?

ex)

function Component () {
  const { query: { page } } = useRouter({ priority: false });
}
function Component () {
  const router = useRouter();
  
  return <button onClick={() => router.push('/', '/', { priority: false })} />
}

To Reproduce

codesandbox

[dclark27]

Adding to this issue, if you change query params to re-trigger data loading, the loading.tsx does not appear. We need this for slow internet connections using our pagination.

Here is a code sandbox reproduction of our issue:

https://codesandbox.io/p/sandbox/muddy-glade-hn895s

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.