-
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
fix(gatsby-recipes): fix for when recipes have multiple NPMPackageJSON resources #26281
Conversation
Gatsby Cloud Build Reportusing-styled-components 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 21s PerformanceLighthouse report
|
Gatsby Cloud Build Reportgatsby-master 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 1m PerformanceLighthouse report
|
Gatsby Cloud Build Reportclient-only-paths 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 22s PerformanceLighthouse report
|
Gatsby Cloud Build Reportusing-reach-skip-nav 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 23s PerformanceLighthouse report
|
Gatsby Cloud Build Reportgatsby 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 5m PerformanceLighthouse report
|
Gatsby Cloud Build Reportgatsby 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 23m |
@@ -5,6 +5,63 @@ const getDiff = require(`../utils/get-diff`) | |||
|
|||
const resourceSchema = require(`../resource-schema`) | |||
|
|||
class Deferred { |
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.
This class is cool and seems useful. Is it or could it be used elsewhere?
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.
possibly! I copied it off stackoverflow haha — we'll probably migrate this whole bit of code that handles writing to a single shared resource (in this case to package.json) to its own library.
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.
🚗
@@ -173,8 +173,14 @@ const handleResource = (resourceName, context, props) => { | |||
resolve(cachedValue) | |||
updateResource(cachedValue) | |||
} else { | |||
// if (fn == `create`) { |
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.
Should we remove these comments and use debug
directly? That way we can toggle them on and off.
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.
yeah... probably — not too worried about having really clean code still 🤷
…N resources (gatsbyjs#26281) * fix(gatsby-recipes): restrict changes to package.json to one at a time * Add message for npmpackagejson + make install output denser * update snapshots
Also threw in improvement to install output