Next Link doesn't check correct manifest key on click
Answered
LaPerm posted this in #help-forum
LaPermOP
I have a Next Link with the href
At first I thought it was the rest param at the end, however, after testing it with another route (
I'm really not sure what's causing this, but it's causing clicking on the link to trigger a hard nav rather than an SPA nav.
Maybe it's the relativity of the path? I don't really want to bother testing that, but If I must I will
This is the pages router, btw
scores/procedures (from the /dashboard/[client]/[practice]/scores page) that on hover, consults the manifest with the correct key (/dashboard/[client]/[practice]/scores/procedures/[[...procedure]]). However, on click, it checks for /dashboard/[client]/[practice]/scores/procedures and, obviously, doesn't find it. (I edited the compiled code to console.log this in the getFilesForRoute function in the route loader)At first I thought it was the rest param at the end, however, after testing it with another route (
/atlas/[year]/[[...measure]]), that route works fine.I'm really not sure what's causing this, but it's causing clicking on the link to trigger a hard nav rather than an SPA nav.
Maybe it's the relativity of the path? I don't really want to bother testing that, but If I must I will
This is the pages router, btw
2 Replies
LaPermOP
This was observed on Next
14.1.1 and 14.1.4LaPermOP
Wow okay this was fixed in
14.2.0Answer