gatsby: Unable to see the progress using "gatsby-plugin-nprogress"
Description
I am trying to integrate “gatsby-plugin-nprogress” into my application, I have done mentioned configuration in gatsby-config.js to add the plugin. But I am not sure how to use it, how can I see loaded on page load and how to operate from applicstion.
Can anyone help me to integrate it within my application?
Steps to reproduce
Expected result
What should happen?
Actual result
What happened.
Environment
- Gatsby version (
npm list gatsby): gatsby@1.9.241 - gatsby-cli version (
gatsby --version): 1.1.49 - Node.js version: 8.9.3
- Operating System: Windows
File contents (if changed):
gatsby-config.js: {
resolve: gatsby-plugin-nprogress,
options: {
color: red,
showSpinner: true,
}
package.json:
gatsby-node.js:
gatsby-browser.js:
gatsby-ssr.js:
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 22 (5 by maintainers)
@sachingvit Progress bar will be only visible in build. In develop we don’t need to fetch resources for other pages, so page changing will not be delayed and therefore progress bar will not show
Awesome plugin!
Can’t confirm if it’s working? How to test?
Install plugin, restart via ‘gatsby develop’, open in Chrome, right click inspect, devtools, Network tab, find ‘throttle’ section (might default to ‘online’) and change to slow 3G. Annnnd now you can see the plugin doing it’s magic!
This would be great info to add to https://www.gatsbyjs.org/packages/gatsby-plugin-nprogress/
I can’t seem to trigger it either, though I also have no problem triggering the one on gatsby.org
The plugin isn’t intended as something you can manually trigger. If you want to manually trigger nprogress, you can import
nprogressdirectly and run it from your own code.And like @ryanditjia mentioned, you’ll only see it if the page load is > 1 second — you can simulate that by loading you site and then reducing the network speed in the devtools.
I see 2 possibilities:
gatsby-config.js. But it’s possible that you’ve made a syntactical error. It should be something like:For anyone who can’t see the plugin, I had the same issue. To resolve it, you’ll also need to install the the original plugin:
once you’ve done that you can import the plugin’s css file
and either some customisation, or create your own css from scratch eg:
Hope this helps.
Yip, me neither. At first I thought was my browser’s dark theme but I see the nprogress element doesn’t exist in the dom anywhere - just the css.
I got the same problem, and I can’t see it on gatsby.org neither.
I’ve also failed to trigger this plugin, with a production build and throttled connection, so I have no way to know if it’s working.
I just checked and it’s working (for me) on gatsbyjs.org - https://cl.ly/0d0o0x420z03
@thebarty Still I am unable to integrate the plugin, but I am able to see the progress bar on my page. You can refer my repo and there is one gatsby-browser.js so I put some small logic there to trigger.
But top off that I am still unable to achieve the behavior of this plugin.
@KyleAMathews I am unable to see loader on gatsby.org
Can you check if you can trigger the progress bar on gatsbyjs.org? We have the plugin installed there.
Any progress on this one? I am also NOT seeing any progress-indicator. Neither in production, nor locally via
gastby build; gatsby serve(and then slowing things down in chrome developer tools).Any idea what else to try?