Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Route did not complete loading: /some-page #25675

Closed
stovmascript opened this issue Jun 1, 2021 · 1 comment · Fixed by #25749 or #27395
Closed

Error: Route did not complete loading: /some-page #25675

stovmascript opened this issue Jun 1, 2021 · 1 comment · Fixed by #25749 or #27395
Labels
please add a complete reproduction The issue lacks information for further investigation

Comments

@stovmascript
Copy link
Contributor

stovmascript commented Jun 1, 2021

What version of Next.js are you using?

10.2.3

What version of Node.js are you using?

12.16.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

custom-server-express

Describe the Bug

While running the dev server, when I click through a couple of pages/, linked by the <Link> component, a full page load happens very often and randomly. This has been reported before: #21543, but in connection with debugging with DevTools.

It works as expected on a production build.

Expected Behavior

Client-side navigation to work without full page loads, except for expected situations, which Fast Refresh warns about and are listed here: https://nextjs.org/docs/basic-features/fast-refresh#how-it-works.

To Reproduce

Unfortunately, this is very hard to reproduce (meaning create a reproduction). I still can't pinpoint the cause of this behaviour. However, you can add this event listener to your _app.js after mount, preserve log in DevTools console, and look for this error right before the full page load.

Router.events.on('routeChangeError', (...yaaarghz) => {
  console.log(...yaaarghz)
})

(optional) You can also add this debugger statement to look through the callstack.

window.addEventListener('beforeunload', () => {
  debugger
})
@stovmascript stovmascript added the bug Issue was opened via the bug report template. label Jun 1, 2021
@timneutkens timneutkens added please add a complete reproduction The issue lacks information for further investigation and removed bug Issue was opened via the bug report template. labels Jun 2, 2021
stovmascript added a commit to monitora-media/next.js that referenced this issue Jun 3, 2021
The new route loader (vercel#19006) will timeout
loading routes after 3.8s (MS_MAX_IDLE_DELAY), but this can easily happen when
running dev on a large app.

Fixes vercel#25675
stovmascript added a commit to monitora-media/next.js that referenced this issue Jul 7, 2021
The new route loader (vercel#19006) will timeout
loading routes after 3.8s (MS_MAX_IDLE_DELAY), but this can easily happen when
running dev on a large app.

Fixes vercel#25675
ijjk added a commit that referenced this issue Jul 12, 2021
* Prevent timeout when loading routes in development

The new route loader (#19006) will timeout
loading routes after 3.8s (MS_MAX_IDLE_DELAY), but this can easily happen when
running dev on a large app.

Fixes #25675

* Delay route loading timeout in development

* refactor: Integrate onBuildCallback into resolvePromiseWithTimeout

* refactor: Tweak for better dead-code elimination

Co-authored-by: JJ Kasper <[email protected]>
flybayer pushed a commit to blitz-js/next.js that referenced this issue Aug 19, 2021
* Prevent timeout when loading routes in development

The new route loader (vercel#19006) will timeout
loading routes after 3.8s (MS_MAX_IDLE_DELAY), but this can easily happen when
running dev on a large app.

Fixes vercel#25675

* Delay route loading timeout in development

* refactor: Integrate onBuildCallback into resolvePromiseWithTimeout

* refactor: Tweak for better dead-code elimination

Co-authored-by: JJ Kasper <[email protected]>
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
3 participants