fix(gatsby-plugin-manifest): fix regression with sharp failing to load #13271
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.
Description
Fairly annoying and confusing bug here--updating sharp in #12757 (which would seem totally reasonable) actually causes the require sharp statement to silently fail in
gatsby-node.js
. I'll open an issue to address the latter part of this statement, but the why of why this happens is helpful.Other plugins (e.g. gatsby-transformer-sharp, gatsby-plugin-sharp, etc. require
sharp
@0.21.3
. The change to0.22.0
caused a tree like:The
require('sharp')
statement in gatsby-node.js would silently fail with:So there are really two issues here:
Related Issues
Fixes #13264