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
Fixing sw.js 404-ing because of pathPrefix not being prefixed to sw.js properly. Fixing #1539 #1540
Conversation
The pathPrefix does not include the trailing slash so we have to make sure to include it so that sw.js gets loaded properly and does not 404
Deploy preview failed. Built with commit cf13675 https://app.netlify.com/sites/gatsbygram/deploys/596e1365424ef2511915c301 |
Deploy preview ready! Built with commit cf13675 |
Deploy preview failed. Built with commit cf13675 https://app.netlify.com/sites/gatsbyjs/deploys/596e1365424ef2511915c2fe |
Deploy preview failed. Built with commit cf13675 https://app.netlify.com/sites/image-processing/deploys/596e1366424ef2511915c310 |
Hiya @gregsqueeb! 👋 This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here. Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! 💪💜 |
Oh wow cool! Thanks so much! |
Hiya @gregsqueeb! 👋 This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here. Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! 💪💜 |
The pathPrefix does not include the trailing slash so we have to make sure to include it so that sw.js gets loaded properly and does not 404