-
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
chore(gatsby-transformer-sharp): remove fragment copying from plugins #19933
chore(gatsby-transformer-sharp): remove fragment copying from plugins #19933
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this, Thomas! It was great pairing with you 💚
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
Holy buckets, @tmaximini — we just merged your PR to Gatsby! 💪💜 Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! |
Description
Since #15284, fragments no longer need to be copied over to the
.cache
directory because gatsby looks throughnode_modules
This PR removes that copying mechanism from
gatsby-transformer-sharp
andgatsby-source-contentful
and updates its peer dependencies to"gatsby": "^2.12.1"