v5.5 Release Notes
firstname.lastname@example.org release (January 2023 #2)
Key highlights of this release:
Also check out notable bugfixes.
Bleeding Edge: Want to try new features as soon as possible? Install
gatsby@next and let us know if you have any issues.
GitHub user FraserThompson put up a feature request to optionally disable MD5 hashing inside
gatsby-source-filesystem. Their site has around ~1000 MP3s (up to 120MB) and 16000 JPGs (around 2-3 MB), so
gatsby-source-fileystem has to ingest a lot of data! While reading the data an MD5 hash is generated for each file to attach the
contentDigest to the
File node. Or in other words: This MD5 hash is used to determine if a file has changed and is used in Gatsby’s caching system.
We’d recommend reading the discussion inside the feature request as it shows a great case of collaboration and how productive open source work can look like. After exploring and debating about the best approach, the PR #37464 was put up. Here’s what has changed:
gatsby-source-filesystemnow uses hash-wasm to calculate the MD5 hash for each file
mtimefile stats and only re-generate the MD5 hash if those changed
Introduce a new
fastHashoption to skip the MD5 hashing altogether. Instead, use the
mtime. On a modern OS this can be considered a robust solution to determine if a file has changed, however on older systems it can be unreliable. Therefore it’s not enabled by default.
FraserThompson also put these changes to the test with this test environment: 4774 files, 3363 images (1-3MB each), 284 MP3s (20-120MB each).
And here are the performance numbers 🚀
|494 seconds (36% decrease)|
|10 seconds (98% decrease)|
As you can see, already the enhancements achieved through
hash-wasm are great! However, take these numbers with a grain of salt as your site will be different from the test environment. You’ll see bigger absolute improvements with a lot of big files.
Last but not least, it’s important to note that the upgrades were made to the
createFileNode function. So if you’re using this utility in your site/plugin, you can also benefit from this.
You can now set the attributes of the
<body> tags using the Head API. Gatsby will automatically incorporate these attributes into the page, with any attributes specified in the Head API taking precedence over those set through Gatsby Server Rendering APIs.
serverDatainto Gatsby Head, via PR #37500
- fix regression with
assetPrefixis used, via PR #37423
pluginOptionsSchemanot being called for local plugins with
gatsby-node.ts, via PR #37443
- support updated
sortargument syntax in
nodeModel.findAllfunction, via PR #37477
- fix back reference fields disapearing after some content updates, via PR #37442
A big Thank You to our community who contributed to this release 💜
- FraserThompson: feat(gatsby-source-filesystem): Only generate hashes when a file has changed, and add an option for skipping hashing PR #37464
- palmiak: chore(docs): Adds Kinsta Application hosting to other services PR #37476
- beadlespouse: fix(gatsby-source-shopify): Use
idas cacheKey for base64 image PR #37397
- chrissantamaria: fix(gatsby): Multi-environment browserslist configs PR #35081
- labifrancis: chore(docs): Update “Minimal Reproduction” instructions PR #37231
- markacola: fix(gatsby): Update
loader.loadPageto return a Promise on error PR #37337
- chawes13: docs: fix v5 release notes slice example PR #37465
- sapiensfio: fix(gatsby-react-router-scroll): fix issues with anchor links PR #37498
- jonrutter: chore(docs): Fix
ts-jestimport statement in Unit Testing Guide PR #37411