-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
beta 8: pages reload in dev mode after compilation #2147
Comments
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 #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 |
I have not.
…On Sat, Jun 17, 2017 at 5:41 PM, Gabe Ragland ***@***.***> 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
<#2147 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAP65YjQm7YyNfHOsI03884EXflMm7DYks5sFEf9gaJpZM4NuUI7>
.
|
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.
The text was updated successfully, but these errors were encountered: