v4.24 Release Notes

Welcome to gatsby@4.24.0 release (September 2022 #2)

Key highlights of this release:

• Gatsby 5 Alpha
• Updating File System Routes on data changes

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.

Previous release notes

Full changelog

Gatsby 5 Alpha

You probably noticed that in the last couple of releases we mostly focused on bug fixes, smaller improvements, and pointing to our RFCs rather than shipping big new features. There’s a simple reason for that: We’re working hard on Gatsby 5! And we’re super excited to share that you can try the Gatsby 5 Alpha today 🎉

For the Alpha the big new feature you’ll be able to test out is Partial Hydration. With Partial Hydration you gain the ability to mark specific parts of your site/application as “interactive”, while the rest of your site is static by default. This will result in shipping less JavaScript to your users and improved Lighthouse scores. For a quick preview of these great features, you can watch the showcase on YouTube

Please take part in the Gatsby 5 Umbrella Discussion, try it out, and let us know what works and doesn’t work. If Discord is more your jam, you can also join the gatsby-5 Discord channel.

Updating File System Routes on data changes

When creating routes using the File System Route API they were correctly created on initial run with gatsby develop. However, on subsequent changes to the underlying sourced data (e.g. Markdown files have their slug field changed) those changes weren’t reflected in the routes. A restart of gatsby develop was necessary.

In PR #36623 we fixed this behavior and any node changes (either by changing local files or through webhook updates) will be reflected in your routes.

Notable bugfixes & improvements

• gatsby-plugin-mdx: Fix the React is not defined error, via PR #36595
• gatsby-remark-copy-linked-files: Add absolutePath to dir function, via PR #36213
• gatsby & gatsby-plugin-mdx: Fix “Multiple root query” error when using a name for your MDX template, via PR #36525
• gatsby-parcel-config: The underlying Parcel config (used for compiling gatsby-config.ts and gatsby-node.ts files) was changed to only handle JavaScript/TypeScript. This aligns the behavior with current Node.js capabilities of gatsby-config.js/gatsby-node.js (e.g. you can’t just import YAML files), via PR #36583
• gatsby: Source maps are available for gatsby-config.ts/gatsby-node.ts files, via PR #36450

Contributors

A big Thank You to our community who contributed to this release 💜

• kxxt: fix(gatsby-core-utils): Use grep -E instead of egrep PR #36648
• Osiris8: chore(docs): Fix Seo imports in tutorial PR #36587
• evanwinter: chore(docs): Update “Layout components” related links PR #36572
• chrisj-skinner: chore(docs): Update storybook main.js docs PR #36627
• alesma: chore(gatsby-plugin-sitemap): Add info about page object to README PR #36582
• benomatis: fix(docs): tiny grammatical correction PR #36630
• Auspicus: feat(gatsby): Enable source maps when compiling Gatsby files in development PR #36450
• kvnang: chore(docs): Fix Partytown forward events examples PR #36613
• karlhorky: feat(gatsby-remark-copy-linked-files): Add absolutePath to dir function PR #36213
• openscript: chore(gatsby): Add loadPageDataSync property to onRenderBody TS type PR #36492
• ebuildy: fix(gatsby-parcel-config): Adjust dependencies PR #36583
• AndrPetrov: fix(gatsby-link): Correct handling of trailingSlash & pathPrefix PR #36542
• treboryx: fix(gatsby): Pass hostname to detect-port PR #36496
• colbywhite: chore(docs): Swap mobile url for regular url PR #36618
• MarcusCole518: chore(docs): Add “Payments Managing” & “Deploying to Fastly” PR #36546
• SilencerWeb: chore(gatsby-source-wordpress): Fix license link PR #36621