Prefetch issues with optional catch-all route

[Bottersnike]

I've got a route setup at pages/[[...page]].js as a fallback route (optionalCatchAll is enabled). Navigating to a route that isn't explicitly defined is successfully landing on this page as would be expected, both when clicking on a link, and when using browser navigation. When hovering over a link, however, next is attempting to prefetch the page. For explicitly defined routes this works fine, however for routes that would fall back to [[...page]].js, requests are being made to /_next/static/....../pages/some/route/here.js, which then 404s. While this doesn't directly impact UX, it causes the console to be spammed with a wall of 404 errors.

Is this intended behaviour, and is there a way to change it without globally disabling prefetching?

[Timer]

It sounds like you're using <Link> incorrectly. Can you please share your component?

[Bottersnike]

Ah that'd do it, tysm. Is there a way I can hook the router in my custom Link component to determine if a route resolves to an explicit path or if it'll fallback to [[...page]].js and apply the props accordingly?

[Timer]

No, but we're going to add this behavior to Next.js automatically soon:
#8207

[Bottersnike]

Ah cool; I'll keep my eyes peeled on that RFC :)

[ivorpad]

@Timer

Prefetch is having issues, tho.

For instance:

href="/store/[[...slug]]" prefetches /store/[products/quiksilver-mens-3-2mm-syncro-series-back-zip-gbs-wetsuit] (notice the open/close brackets)

It's reported here: #14290

[Timer]

Will be fixed on the next canary @ivorpad (^9.4.5-canary.15)!