Gatsby Book Launch

“The missing guide to the modern web” launches on Thursday, Sep 29th: Modular: The Web’s New Architecture

v4.6 Release Notes

Welcome to gatsby@4.6.0 release (January 2022 #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.

Previous release notes

Full changelog


Speeding Up Subsequent Queries

Subsequent queries now get a ~10-15% performance boost! You’ll see this improvement after your first gatsby build for all following runs (unless the cache is cleared). These percentage may defer depending on the complexity of nodes. We were able to achieve this by caching rootNode & trackedRootNodes across instances of graphqlRunner via PR #33695

Tracking Image Changes in Markdown Files

When using an image inside markdown files together with gatsby-remark-images (e.g. ![alt text](./some-image.jpg)) there were cases when a change to the image wasn’t reflected in the site. Changes like resizing or directly editing the image required a gatsby clean in the past. This broken functionality is now fixed with PR #34433 and changed images will now directly show during gatsby develop and gatsby build.

New Major Version for gatsby-plugin-utils

You can configure plugin options for your plugins and unit test the options schema using helper functions from gatsby-plugin-utils. The schema validation for the options schema now does not throw errors anymore on warnings like unknown keys (see PR that implemented this for more information). This fixed an issue where default values where not passed through to the plugin if e.g. unknown keys were used.

Here’s a short list of changes you’ll need to make or be aware of:

  • pluginOptionsSchema returns warnings instead of errors now for unknown keys
  • testPluginOptionsSchema now returns warnings and hasWarnings in addition to the existing values
  • Default options you set in your plugin option schema are now correctly passed through to the plugin, even when a user sets unknown keys

Migration

Here’s a short before/after example on how to migrate your test when you’re checking for unknown keys.

Before:

After:

Notable Bugfixes & Improvements

  • gatsby-plugin-manifest: Generate icons sequentially, via PR #34331
  • create-gatsby: Fixed an issue where user-provided GATSBY_TELEMETRY_DISABLED environment variable did not disable telemetry, via PR #34495
  • gatsby-sharp: Create more resilient wrapper around sharp, via PR #34339
  • gatsby-source-contentful: Enable tag support for assets, via PR #34480
  • gatsby: Optimized queries that filter just on id, via PR #34520

Contributors

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

Edit this page on GitHub
© 2022 Gatsby, Inc.