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.
Some additional improvements to build/deploy performance.
It's been bothering me that the Netlify build often needs to redeploy thousands of files for no apparent reason after merging PRs that often don't change much. I've been diffing build outputs to understand why.
the
react-select
component library increments element ids internally by default. This is causing a problem because Gatsby builds using parallel worker threads that execute in an unpredictable order, so a page will very likely end up with a different select component id between each build. Explicitly setting theinstanceId
prop fixes the problem.https://github.com/JedWatson/react-select/blob/c350a124f8de853a79e0158578d438a35e67e63e/packages/react-select/src/Select.tsx#L638-L639
the
TopBar
component that displays today's date is captured in HTML during the build phase. It creates some visual flickering because the date in the markup is often not the same as after hydration. It also forces every HTML page to be redeployed on a new build if the last build didn't happen on the same date (UTC). This PR only displays the date after React hydration to address the problem.topbar-date-flicker.mp4
webpackCompilationHash
value. See First incremental build rebuilds all HTML pages gatsbyjs/gatsby#33450. The fix was a breaking change for Gatsby 4 and was supposed to be rolled out in v5 - but I think it might've slipped. Not much we can do about this for now.