Documentation

TutorialHow-To GuidesReferenceConceptual Guides

v3 Docsv2 Docsv1 Docs
Sign Up for Free

v4.3 Release Notes

Welcome to gatsby@4.3.0 release (November 2021 #3)

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.

Previous release notes

Full changelog


Content Sync Improvements

The createNodeManifest action gets a performance boost.

We no longer hash page-data.json files and include that hash in node manifest files in order to determine if that page-data has deployed. Instead we include the manifest id passed to createNodeManifest within the page-data file as a more performant way to check if the corresponding data for a data update has deployed and become publicly available online. This allows us to create more node manifest files than before, making services such as Content Sync more reliable, in more situations.

We’ve also added a new updatedAtUTC argument to the action, passing a date here allows Gatsby to determine wether or not the node manifest file should be created or not. If the date is older than 30 days (by default) the node manifest will not be created. Users can change this default by setting the NODE_MANIFEST_MAX_DAYS_OLD environment variable to any number of days.

Use renderToPipeableStream React 18 API

Gatsby switched to renderToPipeableStream instead of pipeToNodeWritable from older React 18 alpha versions. Now with React 18 beta and the new alphas renderToPipeableStream is the recommend API for Server Side Rendering.

Notable bugfixes & improvements

  • gatsby: Don’t retain logs in Gatsby Cloud, via PR #34045
  • gatsby-source-shopify: Fix peerDependencies for gatsby-plugin-image via PR #34044
  • gatsby: Reduce cost of sourcing after the initial, via PR #33692

Contributors

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

Edit this page on GitHub
© 2022 Gatsby, Inc.