CORB errors in Chrome when using assetPrefix and gatsby-plugin-offline
See original GitHub issueDescription
When using Gatsby with assetPrefix
option and gatsby-plugin-offline
I receive multiple CORB errors while making PWA test in Lighthouse (Chrome Version 81.0.4044.138).
Steps to reproduce
Visit https://gatsby-corb-bugreport.now.sh using latest Chrome version in incognito mode. Open Audits tab in devtools (Lighthouse) and run PWA test.
Reproduction repo: https://github.com/paveli/gatsby-corb-bugreport (default starter with several pages, assetPrefix
with BunnyCDN setup, gatsby-plugin-offline
setup)
Expected result
Should work without CORB warnings. Should receive access to remote json files.
Actual result
Browser can’t access remote json files.
Environment
System: OS: macOS 10.15.4 CPU: (8) x64 Intel® Core™ i7-6700HQ CPU @ 2.60GHz Shell: 3.2.57 - /bin/bash Binaries: Node: 13.12.0 - /usr/local/bin/node Yarn: 1.12.3 - /usr/local/bin/yarn npm: 6.14.4 - /usr/local/bin/npm Languages: Python: 2.7.15 - /usr/local/bin/python Browsers: Chrome: 81.0.4044.138 Firefox: 68.0.2 Safari: 13.1 npmGlobalPackages: gatsby-cli: 2.7.54
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top GitHub Comments
I’ll be looking into this bug today 😃
Hi, any updates on this issue? If no one is working on it right now, maybe I can try to help fixing it with some guidance from core team?
@wardpeet @danabrit