Error: Route did not complete loading: /projects

[dawksh]

What version of Next.js are you using?

10.0.5

What version of Node.js are you using?

14.15.0

What browser are you using?

Chrome

What operating system are you using?

Windows 10

How are you deploying your application?

Vercel

Describe the Bug

I am trying to build a simple route for my portfolio. The route is '/projects'. I've added a projects.js file in the pages directory with the logical code and when I use next/link for client side transition, I get an error: Route did not complete loading: "projects".
When I use regular anchor tag for routing, there is no issue.

Expected Behavior

It should change the route to the destined page without any error.

To Reproduce

import styles from '../styles/Home.module.css'
import Link from 'next/link'

export default function Footer() {
    return (
        <>
            <div className={styles.link}>
                <a href="https://github.com/devdaksh" target="__blank">github</a>
                <a href="https://twitter.com/dawksh" target="__blank">twitter</a>
                <a href="https://devdaksh.hashnode.dev" target="__blank">blogs</a>
                <a href="mailto:akshd@outlook.com">email</a>
                <Link href="/projects" >
                    <a>projects</a>
                </Link>
            </div>
        </>
    )
}

This is a screenshot of the error

[donpark]

Seeing the same on macOS with:

• development build
• production build
• on page with <Link> tag
• on page routed to via <Link> tag.

Same 10.0.5 version of Next.js running on Node 14.15.4.

I also tested previous minor versions and found that 10.0.1 is the last version that does not throw this error. 10.0.0 is fine also.

[mikkelramlov]

Same error here. +1

[retr00exe]

I'm facing the same error too on my project. The official next.js website also has this issue if you open chrome developer tools and click one of its routes a couple of times.

[GaddMaster]

I am also getting this error. I am not far off the official tutorials. I am pretty sure I was getting it while following the site basic tutorial.

[bpas247]

This error seems to be originated from here, which was added in #19006 (and was released in v10.0.2).

I'm not entirely sure if this code itself is what's causing the error to be thrown, I would assume not since we would have noticed it earlier on, so something else seems to be causing the idleTimeout promise to be resolved earlier than the onBuildManifest promise is being resolved.

In other words, something is causing onBuildManifest to take way longer than expected.

[dbo]

IMO this is not a real issue, but rather annoying if you've enabled Pause on exceptions in devtools. The Promise.race correctly resolves the route loading, the timeout promise is just dangling after and devtools stops on it.

[GaddMaster]

Yep, pause on exception triggers it

[donpark]

Chrome has a similar 'ghost' exception bug with FileSystemWritableFileStream when close (sometimes write) is called that also goes away when "Pause on exceptions" is disabled.

I'd treat this as a real bug because:

1. It's not a corner case.
2. It's a fixable bug AFAIK.
3. Developers among users of apps built using Next.js may see it and report it as a bug which multiplies unnecessary waste of resources.

My advice is to make idletTimeout cancellable and have the good path cancel timeout when it finishes first. It's a common enough pattern and cancellable Promise is not expected to arrive for a while so I think it's worth investing some time on.

[dbo]

I agree, you could look at it as a dev issue, even though it does not have impact on production sites, and I totally agree about (3), unnecessary issue noise.

[timkindberg]

We are experiencing this issue in our automated tests, it's failing our suite. I was able to reproduce this error without having "pause on exception" turned on.

[ocodista]

I'm also seeing this error on next@10.2

[ghost]

The exception is annoying and wastes developer's time. It would be lovely to have it fixed, rather than having to ignore it. Here is next@10.2.2

[timneutkens]

Please open a new issue with a complete reproduction and we'll have a look!

[balazsorban44]

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.