-
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] gatsby-plugin-offline non index roots don't load when offline #6081
Comments
This is from a project upgrading from v1 where the functionality worked fine previously |
Could you link to a repo or create a small example repo that does this? |
https://github.com/jamesadarich/james.adarich.com My V2 migration progress is visible as a pull request |
@jamesadarich I wasn't able to get your site to build - either In your repo I did the following steps:
For both branches, the generated site code looks like this: Opening If I open the file anyway, it renders like:
Any ideas on what's causing that? |
@m-allanson I believe this is because the assets are gzipped for production and |
Hey @KyleAMathews, I've just updated all |
Do you have a way to reproduce this? Can you see the problem on gatsbyjs.com? |
Description
When I return to a page offline that I have previously loaded whilst online the page does not load and shows the browser standard no internet connection page. When I do this on the index page the page loads fine and I can navigate to the pages that don't work. All the pages that don't work are built from markdown dynamically as they are blog articles.
Steps to reproduce
navigate to a blog article
take device offline
reload the page
notice standard no internet page
navigate to index page
take device offline
reload the page
notice the site loads fine
Expected result
The site should load as if offline
Actual result
The site failed to load
Environment
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Binaries:
npm: 5.6.0 - ~\AppData\Roaming\npm\npm.CMD
Browsers:
Edge: 42.17134.1.0
npmPackages:
gatsby: next => 2.0.0-beta.4
gatsby-cli: next => 2.0.0-beta.2
gatsby-image: next => 2.0.0-beta.2
gatsby-plugin-canonical-urls: next => 2.0.0-beta.2
gatsby-plugin-favicon: ^2.1.1 => 2.1.1
gatsby-plugin-google-tagmanager: next => 2.0.0-beta.2
gatsby-plugin-manifest: next => 2.0.2-beta.2
gatsby-plugin-offline: next => 2.0.0-beta.2
gatsby-plugin-react-helmet: next => 3.0.0-beta.2
gatsby-plugin-sass: next => 2.0.0-beta.2
gatsby-plugin-sharp: next => 2.0.0-beta.2
gatsby-plugin-sitemap: next => 2.0.0-beta.2
gatsby-plugin-typescript: next => 2.0.0-beta.2
gatsby-remark-copy-linked-files: next => 2.0.0-beta.2
gatsby-remark-images: next => 2.0.1-beta.3
gatsby-remark-prismjs: next => 3.0.0-beta.2
gatsby-source-filesystem: next => 2.0.1-beta.2
gatsby-transformer-remark: next => 2.1.1-beta.2
gatsby-transformer-sharp: next => 2.1.1-beta.2
error The system cannot find the path specified.
Error: The system cannot find the path specified.
File contents (if changed)
gatsby-config.js
: N/Apackage.json
: N/Agatsby-node.js
: N/Agatsby-browser.js
: N/Agatsby-ssr.js
: N/AThe text was updated successfully, but these errors were encountered: