-
Notifications
You must be signed in to change notification settings - Fork 10
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
Preloading module doesn't work #2
Comments
Could you reduce this some more? Or at least create an example of the bug that I can run by clicking a link? For instance, here's a script loading another preloaded script, but the preloading works fine here, so there's something different between my example & yours. You'll probably discover what that is while you're making the reduced test. This might help: https://css-tricks.com/reduced-test-cases/ |
Thanks for your patience. Here's the live demo: http://preloadjsmodules.pancakeapps.com/ Here are the files for this reduced test case: https://github.com/anthonygore/preload-js-modules |
Cheers! Here's a further reduced case with a fix: https://module-load-preload.glitch.me/. I was roughly in the right direction with https://twitter.com/jaffathecake/status/908561563212144643. You need the |
@jakearchibald thanks for your time on this! Got some questions though:
|
The fix is putting
You're talking about https://module-load-preload.glitch.me/ yeah? I don't see a warning in Chrome 61 or 63. Which version are you using?
The default value is fine (which is |
Thanks, @jakearchibald. I'm on Chrome 61 and that fixed it perfectly for me. |
I was on Chrome 60. Maybe that's the reason. Thanks a lot for the explanations btw, very helpful and clear! |
Referring to the branch preload and to the file
index.html
:https://github.com/anthonygore/vue-single-file-js-components/blob/preload/index.html
app.js
importsSingleFileComponent.js
. To speed the app up, I thought I could preloadSingleFileComponent.js
by adding this toindex.html
:But it doesn't work. I get this warning in Chome 61:
It also seems that Chrome loads
SingleFileComponent.js
again even though it should already be available.The text was updated successfully, but these errors were encountered: