v4.23 Release Notes
email@example.com release (September 2022 #1)
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.
We are adding a new API that we are calling “Slices”. By using a new
<Slice /> React component in combination with a
src/slices directory or
createSlice API for common UI features, Gatsby will be able to build and deploy individual pieces of your site that had content changes, not entire pages.
To create a slice, simply:
Create the slice by adding a
slices/footer.jsfile, or using the
<Slice />component on your site, providing an
aliasstring prop, where
aliasis either name of the file (in our case,
footer). Any additional props passed will be handed down to the underlying component.
To read more, head over to RFC: Slices API. We appreciate any feedback there.
sort and aggregation fields in Gatsby GraphQL Schema
We are proposing Breaking Changes for the next major version of Gatsby to our GraphQL API. The goal of this change is increasing performance and reducing resource usage of builds. Proposed changes impact
sort and aggregation fields (
Basic example of proposed change:
To read more, head over to RFC: Change to sort and aggregation fields API. We appreciate any feedback there.
Notable bugfixes & improvements
svgodependency to fix vulnerability, via #36445
- Make package work with npm 8.5, via #36498
- Ensure plugins are installed correctly, via #36566
A big Thank You to our community who contributed to this release 💜
- CobyPear: chore(gatsby): Update
- IObert: chore(docs): Fix path to components in part 6 PR #36463
- subhoghoshX: fix(docs): fix creating routes code snippet PR #36479
- dreibona: chore(docs): Fix
gatsby-source-filesystemtypo PR #36471