-
Notifications
You must be signed in to change notification settings - Fork 403
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
Prerendering is not working #390
Comments
Thanks for the details @kireerik. I added the ![]() and it looks like the resume page is still prefetched as expected, speculation rules is injected and the page is prerendered: ![]() Just a side note that the latest quicklink release has not included the update to remove 1 prerender limit, hence the resume page is not included in the speculation rules. Did you try with |
I tried the Can you release ? |
|
@kireerik Great to see that the prerender option works to add the speculation rules on your page. Which tool did you use to observe whether the page is prerendered successfully. This new preloading panel in DevTools and testing it in Canary will be the most reliable way to test.
As for the release, hope it can be released soon too. @XhmikosR / @addyosmani have you planned for the next release yet? Thank you! |
@hadyan: IIRC, @addyosmani wanted to make the next version a minor release (I personally would land any other breaking changes and make it v3.0.0 to be safe since the dist file filenames have changed IIRC). I don't have push rights on npm AFAICT so it's up to @addyosmani to cut the new version :) |
and (when enabled) there is no prefetching either.
example:
Refo
To Reproduce
Enable the option around this line:
Version:
The text was updated successfully, but these errors were encountered: