Bumped gatsby-source-filesystem to v2.11.1 #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull from flamelink/gatsby-source-flamelink master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The gatsby-source-flamelink plugin is using a very old version of gatsby-source-filesystem, causing a wide range of build errors. The first error is the failure to download remote images during build, and the second error is the inability to find images in the cache folder.
I bumped gatsby-source-filesystem to the newest version available that still uses gatsby v.2, so that the update would not cause any breaking changes.
I tested this solution with my own project, and it appears to work nicely. Build times were also significantly faster, as there were no longer a need to set a max number of concurrent downloads during build time.
This PR will likely fix #50