Search code, repositories, users, issues, pull requests...

`v5.13.6`

`v5.13.5`

`v5.13.4`

`v5.13.3`

`v5.13.2`

`v5.13.1`

`v5.13.0`: v5.13.0

Welcome to gatsby@5.13.0 release (December 2023 #1)

Key highlight of this release:

Custom Image and File CDN URL generators

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.12.12`

`v5.12.11`

`v5.12.10`

`v5.12.9`

`v5.12.8`

`v5.12.7`

`v5.12.6`

`v5.12.5`

`v5.12.4`

`v5.12.3`

`v5.12.2`

`v5.12.1`

`v5.12.0`: v5.12.0

Welcome to gatsby@5.12.0 release (August 2023 #1)

Key highlight of this release:

Adapters

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.11.0`: v5.11.0

Welcome to gatsby@5.11.0 release (June 2023 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.10.0`

`v5.9.1`

`v5.9.0`

`v5.8.1`

`v5.8.0`

`v5.7.0`: v5.7.0

Welcome to gatsby@5.7.0 release (February 2023 #2)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.6.1`

`v5.6.0`: v5.6.0

Welcome to gatsby@5.6.0 release (February 2023 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.5.0`

`v5.4.2`

`v5.4.1`

`v5.4.0`: v5.4.0

Welcome to gatsby@5.4.0 release (January 2023 #1)

The whole team took time off for a much deserved winter break and we hope you had relaxing holidays, too! Before the break we spent time doing maintenance work such as updating internal dependencies or fixing some smaller bugs here and there. In case you missed it, we shipped ES Modules (ESM) in Gatsby files in the last release.

So check out the notable bugfixes section to learn more.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.3.3`

`v5.3.2`

`v5.3.1`

`v5.3.0`: v5.3.0

Welcome to gatsby@5.3.0 release (December 2022 #1)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.2.0`: v5.2.0

Welcome to gatsby@5.2.0 release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.1.0`: v5.1.0

Welcome to gatsby@5.1.0 release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
Partial Hydration allows you to ship only the necessary JavaScript to the browser

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v5.0.1`

`v5.0.0`: v5.0.0

Welcome to gatsby@5.0.0 release (November 2022 #1)

Key highlights of this release:

Slice API - Only re-build individual slices of your page
Partial Hydration (Beta) - Improve frontend performance by shipping less JavaScript
GraphiQL v2 - An all new UI with features like dark mode, tabs, and persisted state
Performance Improvements

Major dependency updates:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

`v4.25.9`

`v4.25.8`

facebook/react (react)

`v18.3.1`

`v18.3.0`

`v18.2.0`

React DOM

Provide a component stack as a second argument to onRecoverableError. (@gnoff in #24591)
Fix hydrating into document causing a blank page on mismatch. (@gnoff in #24523)
Fix false positive hydration errors with Suspense. (@gnoff in #24480 and @acdlite in #24532)
Fix ignored setState in Safari when adding an iframe. (@gaearon in #24459)

React DOM Server

Pass information about server errors to the client. (@salazarm and @gnoff in #24551 and #24591)
Allow to provide a reason when aborting the HTML stream. (@gnoff in #24680)
Eliminate extraneous text separators in the HTML where possible. (@gnoff in #24630)
Disallow complex children inside <title> elements to match the browser constraints. (@gnoff in #24679)
Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@jplhomer in #24641)

Server Components (Experimental)

Add support for useId() inside Server Components. (@gnoff in #24172)

`v18.1.0`

React DOM

Fix the false positive warning about react-dom/client when using UMD bundle. (@alireza-molaee in #24274)
Fix suppressHydrationWarning to work in production too. (@gaearon in #24271)
Fix componentWillUnmount firing twice inside of Suspense. (@acdlite in #24308)
Fix some transition updates being ignored. (@acdlite in #24353)
Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)
Fix throttling of revealing Suspense fallbacks. (@sunderls in #24253)
Fix an inconsistency in whether the props object is the same between renders. (@Andarist and @acdlite in #24421)
Fix a missing warning about a setState loop in useEffect. (@gaearon in #24298)
Fix a spurious hydration error. (@gnoff in #24404)
Warn when calling setState in useInsertionEffect. (@gaearon in #24295)
Ensure the reason for hydration errors is always displayed. (@gaearon in #24276)

React DOM Server

Fix escaping for the bootstrapScriptContent contents. (@gnoff in #24385)
Significantly improve performance of renderToPipeableStream. (@gnoff in #24291)

ESLint Plugin: React Hooks

Fix false positive errors with a large number of branches. (@scyron6 in #24287)
Don't consider a known dependency stable when the variable is reassigned. (@afzalsayed96 in #24343)

Use Subscription

Replace the implementation with the use-sync-external-store shim. (@gaearon in #24289)

`v18.0.0`

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features

React

useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.

React DOM Client

These new APIs are now exported from react-dom/client:

createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

renderToPipeableStream: for streaming in Node environments.
renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

facebook/react (react-dom)

`v18.3.1`

`v18.3.0`

`v18.2.0`

React DOM

Provide a component stack as a second argument to onRecoverableError. (@gnoff in #24591)
Fix hydrating into document causing a blank page on mismatch. (@gnoff in #24523)
Fix false positive hydration errors with Suspense. (@gnoff in #24480 and @acdlite in #24532)
Fix ignored setState in Safari when adding an iframe. (@gaearon in #24459)

React DOM Server

Pass information about server errors to the client. (@salazarm and @gnoff in #24551 and #24591)
Allow to provide a reason when aborting the HTML stream. (@gnoff in #24680)
Eliminate extraneous text separators in the HTML where possible. (@gnoff in #24630)
Disallow complex children inside <title> elements to match the browser constraints. (@gnoff in #24679)
Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@jplhomer in #24641)

Server Components (Experimental)

Add support for useId() inside Server Components. (@gnoff in #24172)

`v18.1.0`

React DOM

Fix the false positive warning about react-dom/client when using UMD bundle. (@alireza-molaee in #24274)
Fix suppressHydrationWarning to work in production too. (@gaearon in #24271)
Fix componentWillUnmount firing twice inside of Suspense. (@acdlite in #24308)
Fix some transition updates being ignored. (@acdlite in #24353)
Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)
Fix throttling of revealing Suspense fallbacks. (@sunderls in #24253)
Fix an inconsistency in whether the props object is the same between renders. (@Andarist and @acdlite in #24421)
Fix a missing warning about a setState loop in useEffect. (@gaearon in #24298)
Fix a spurious hydration error. (@gnoff in #24404)
Warn when calling setState in useInsertionEffect. (@gaearon in #24295)
Ensure the reason for hydration errors is always displayed. (@gaearon in #24276)

React DOM Server

Fix escaping for the bootstrapScriptContent contents. (@gnoff in #24385)
Significantly improve performance of renderToPipeableStream. (@gnoff in #24291)

ESLint Plugin: React Hooks

Fix false positive errors with a large number of branches. (@scyron6 in #24287)
Don't consider a known dependency stable when the variable is reassigned. (@afzalsayed96 in #24343)

Use Subscription

Replace the implementation with the use-sync-external-store shim. (@gaearon in #24289)

`v18.0.0`

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features

React

useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.

React DOM Client

These new APIs are now exported from react-dom/client:

createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

renderToPipeableStream: for streaming in Node environments.
renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

facebook/react (react-is)

`v18.3.1`

`v18.3.0`

`v18.2.0`

React DOM

Provide a component stack as a second argument to onRecoverableError. (@gnoff in #24591)
Fix hydrating into document causing a blank page on mismatch. (@gnoff in #24523)
Fix false positive hydration errors with Suspense. (@gnoff in #24480 and @acdlite in #24532)
Fix ignored setState in Safari when adding an iframe. (@gaearon in #24459)

React DOM Server

Pass information about server errors to the client. (@salazarm and @gnoff in #24551 and #24591)
Allow to provide a reason when aborting the HTML stream. (@gnoff in #24680)
Eliminate extraneous text separators in the HTML where possible. (@gnoff in #24630)
Disallow complex children inside <title> elements to match the browser constraints. (@gnoff in #24679)
Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@jplhomer in #24641)

Server Components (Experimental)

Add support for useId() inside Server Components. (@gnoff in #24172)

`v18.1.0`

React DOM

Fix the false positive warning about react-dom/client when using UMD bundle. (@alireza-molaee in #24274)
Fix suppressHydrationWarning to work in production too. (@gaearon in #24271)
Fix componentWillUnmount firing twice inside of Suspense. (@acdlite in #24308)
Fix some transition updates being ignored. (@acdlite in #24353)
Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)
Fix throttling of revealing Suspense fallbacks. (@sunderls in #24253)
Fix an inconsistency in whether the props object is the same between renders. (@Andarist and @acdlite in #24421)
Fix a missing warning about a setState loop in useEffect. (@gaearon in #24298)
Fix a spurious hydration error. (@gnoff in #24404)
Warn when calling setState in useInsertionEffect. (@gaearon in #24295)
Ensure the reason for hydration errors is always displayed. (@gaearon in #24276)

React DOM Server

Fix escaping for the bootstrapScriptContent contents. (@gnoff in #24385)
Significantly improve performance of renderToPipeableStream. (@gnoff in #24291)

ESLint Plugin: React Hooks

Fix false positive errors with a large number of branches. (@scyron6 in #24287)
Don't consider a known dependency stable when the variable is reassigned. (@afzalsayed96 in #24343)

Use Subscription

Replace the implementation with the use-sync-external-store shim. (@gaearon in #24289)

`v18.0.0`