-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[v2] Warning in browser console during gatsby serve (after build) #7713
Comments
I'm getting this same issue, both when using |
I am getting the same issue, throwing 7 of the same warnings for various js bundles |
same here |
I am as well. @rtm619 did you find solution? |
I'm getting the following locally & running in S3 and Netlify:
|
The site of Gatsby and my new npm.cardiv.de are throwing the same warnings for me (Chrome), but both for a json file which seems to come from the offline plugin. The same as @coughlanio mentioned. Maybe because it's a fallback file that doesn't need to be loaded in Chrome (and therefore, the browser doesn't use that file)? |
We should defenitely drop If anyone would want to take a stab at this: In there we would want to implement
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Replying. I'll take a stab at this. |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
At first, this only happened locally, but now it's also happening on Netlify. Any resolution for this yet? |
Same |
Same here! |
The issue is still there using:
|
I am getting the same issue. any update? |
A few months later and I'm still experiencing the same issue. Any updates? |
Yeah i'm still seeing this issue |
Same. Just updated from gatsby v2 to v3 |
Any update how to fix this issue |
same issue on firefox, gatsby-plugin-offline": "^3.0.32 |
Summary
Chrome throws a warning in console during gatsby serve.
Relevant information
The warning is :
The resource http://localhost:9000/static/d/708/path---en-869-cd4-rxXbyoDAkJ1rXH07VFHKZjmdHQI.json was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate
asvalue and it is preloaded intentionally.
It doesn't cause any problems, just throws a warning. Any clue as to why it does?
Environment (if relevant)
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Binaries:
Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 5.6.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 41.16299.611.0
npmPackages:
gatsby: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-image: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-link: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-canonical-urls: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-google-analytics: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-google-tagmanager: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-i18n: 0.4.2 => 0.4.2
gatsby-plugin-manifest: 2.0.2-rc.0 => 2.0.2-rc.0
gatsby-plugin-offline: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-purify-css: 2.2.1 => 2.2.1
gatsby-plugin-react-helmet: 3.0.0-rc.0 => 3.0.0-rc.0
gatsby-plugin-remove-trailing-slashes: ^1.0.9 => 1.0.9
gatsby-plugin-robots-txt: 1.3.0 => 1.3.0
gatsby-plugin-sharp: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-plugin-sitemap: 2.0.0-rc.0 => 2.0.0-rc.0
gatsby-source-contentful: 2.0.1-rc.0 => 2.0.1-rc.0
gatsby-transformer-remark: 2.1.1-rc.0 => 2.1.1-rc.0
gatsby-transformer-sharp: 2.1.1-rc.0 => 2.1.1-rc.0
The text was updated successfully, but these errors were encountered: