-
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
Show progress for downloading remote files #10948
Comments
Also related: #6125 Over 11 minutes on My suggestion in the linked issue was to consider a I have also noted in that example project, that when an image was sourced remotely(at least in that project/unsplash case), if the transfer fails during, no error was raised, instead the build is considered successful and the images that failed will display their partially downloaded contents. Should I raise another issue about that? I'm not quite sure how I could setup a reproducible project to demonstrate or if Gatsby would have anyway to confirm the remote download was successful? |
I would love to give this a go since i use that api quite often. I am assigning it to myself to avoid double work. |
* [gatsby-source-filesystem] Add progress bar Fix: #10948 * Change wording on progress bar
* [gatsby-source-filesystem] Add progress bar Fix: gatsbyjs#10948 * Change wording on progress bar
* [gatsby-source-filesystem] Add progress bar Fix: gatsbyjs#10948 * Change wording on progress bar
Many plugins rely on
createRemoteFileNode
fromgatsby-source-filesystem
to download files from remote systems. E.g. gatsby-source-wordpress downloads all the files from the wordpress instance so you can include them in your site and do data transformations e.g. image thumbnail creation.This is great but some systems have many files which can take a long time to download. This downloading can cause confusion because the Gatsby bootstrap just stalls out for no apparent reason.
To start improving this, the first thing we need to do is to show a progress bar & current status for downloads.
Related issue about problems this causes with wordpress #6654
The text was updated successfully, but these errors were encountered: