Something I just noticed after upgrading from beta 6 to beta 8. In dev mode, clicking a Link to an uncompiled page causes a reload of the current page.
Repro:
<Link> wrapping an <a> to a page that hasn't been compiled yetWhat should happen:
What does happen:
Seeing this in Chrome. I'm noticing that the server is showing a 200 to the previous page's URL, so it's a full page load rather than just re-rendering client side.
I'm also seeing this issue on beta 8 and beta 9.
Yep, seeing the same thing here. (running on beta9)
Also have this problem on 2.4.1 (was fine on 2.4.0)
Fixed with https://github.com/zeit/next.js/pull/2171
Still seeing this problem on beta 13.
@MindRave @finneganh Are you also still seeing this issue with the latest beta?
EDIT: Okay problem solved. For some reason NPM was installing beta 9 even with "next": "^3.0.0-beta16" in my package.json and doing a fresh npm install (after deleting /npm_modules and package-lock.json). I had to do npm install next@beta --save to get beta 16. With the latest beta I'm no longer seeing this issue.
I have not.
On Sat, Jun 17, 2017 at 5:41 PM, Gabe Ragland notifications@github.com
wrote:
@MindRave https://github.com/mindrave @finneganh
https://github.com/finneganh Are you also still seeing this issue with
the latest beta?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zeit/next.js/issues/2147#issuecomment-309241911, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAP65YjQm7YyNfHOsI03884EXflMm7DYks5sFEf9gaJpZM4NuUI7
.
Most helpful comment
I'm also seeing this issue on beta 8 and beta 9.