"Fossies" - the Fresh Open Source Software Archive

Member "gatsby-gatsby-5.10.0/docs/docs/reference/release-notes/v4.18/index.md" (16 May 2023, 4839 Bytes) of package /linux/www/gatsby-gatsby-5.10.0.tar.gz:

As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

A hint: This file contains one or more very long lines, so maybe it is better readable using the pure text view mode that shows the contents as wrapped lines within the browser window.

Welcome to gatsby@4.18.0 release (July 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.

Previous release notes

Full changelog

typesOutputPath option for GraphQL Typegen

We saw great adoption of the GraphQL Typegen feature we've added in the 4.15 Release. We've heard that the location of the automatically generated TypeScript definitions file should be configurable. By default, it's generated in the src/gatsby-types.d.ts location.

You're now able to specify the location of the generated types using the typesOutputPath option. The graphqlTypegen option accepts both a boolean and an object now. If you don't pass an object (but graphqlTypegen: true), the default value for each option will be used.

module.exports = {
  graphqlTypegen: {
    typesOutputPath: `gatsby-types.d.ts`,
  },
}

The path is relative to the site root, in the example above the file would be generated at <root>/gatsby-types.d.ts. For more details and any future options, see the Gatsby Config API.

Server Side Rendering (SSR) in development

Shortly before v4 release, we disabled DEV_SSR flag because getServerData was not properly handled. In this release, we handled getServerData properly and restored the flag. Now you can add the DEV_SSR flag to your gatsby-config file so you can spot and fix SSR errors (like trying to access the window object) during development.

Open RFCs

We continue to have ongoing RFCs that we’d like your input on. Please give it a read, if applicable a try, and leave feedback!

Notable bugfixes & improvements

Contributors

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