Build blazing fast, modern apps and websites with React

Last update: Jun 19, 2022

Gatsby

Gatsby v2

βš›οΈ πŸ“„ πŸš€

Fast in every way that matters

Gatsby is a free and open source framework based on React that helps developers build blazing fast websites and apps

Gatsby is released under the MIT license. Current CircleCI build status. Current npm package version. Downloads per month on npm. Total downloads on npm. PRs welcome! Follow @gatsbyjs

Quickstart Β· Tutorial Β· Plugins Β· Starters Β· Showcase Β· Contribute Β· Support: Twitter & Discord

Gatsby is a modern web framework for blazing fast websites.

  • Go Beyond Static Websites. Get all the benefits of static websites with none of the limitations. Gatsby sites are fully functional React apps so you can create high-quality, dynamic web apps, from blogs to e-commerce sites to user dashboards.

  • Use a Modern Stack for Every Site. No matter where the data comes from, Gatsby sites are built using React and GraphQL. Build a uniform workflow for you and your team, regardless of whether the data is coming from the same backend.

  • Load Data From Anywhere. Gatsby pulls in data from any data source, whether it’s Markdown files, a headless CMS like Contentful or WordPress, or a REST or GraphQL API. Use source plugins to load your data, then develop using Gatsby’s uniform GraphQL interface.

  • Performance Is Baked In. Ace your performance audits by default. Gatsby automates code splitting, image optimization, inlining critical styles, lazy-loading, prefetching resources, and more to ensure your site is fast β€” no manual tuning required.

  • Host at Scale for Pennies. Gatsby sites don’t require servers so you can host your entire site on a CDN for a fraction of the cost of a server-rendered site. Many Gatsby sites can be hosted entirely free on services like GitHub Pages and Netlify.

Learn how to use Gatsby for your next project.

What’s In This Document

πŸš€ Get Up and Running in 5 Minutes

You can get a new Gatsby site up and running on your local dev environment in 5 minutes with these four steps:

  1. Install the Gatsby CLI.

    npm install -g gatsby-cli
    
  2. Create a Gatsby site from a Gatsby starter.

    Get your Gatsby blog set up in a single command:

    # create a new Gatsby site using the default starter
    gatsby new my-blazing-fast-site
  3. Start the site in develop mode.

    Next, move into your new site’s directory and start it up:

    cd my-blazing-fast-site/
    gatsby develop
  4. Open the source code and start editing!

    Your site is now running at http://localhost:8000. Open the my-blazing-fast-site directory in your code editor of choice and edit src/pages/index.js. Save your changes, and the browser will update in real time!

At this point, you’ve got a fully functional Gatsby website. For additional information on how you can customize your Gatsby site, see our plugins and the official tutorial.

πŸŽ“ Learning Gatsby

Full documentation for Gatsby lives on the website.

  • For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

  • To dive straight into code samples head to our documentation. In particular, check out the β€œGuides”, β€œAPI Reference”, and β€œAdvanced Tutorials” sections in the sidebar.

We welcome suggestions for improving our docs. See the β€œhow to contribute” documentation for more details.

Start Learning Gatsby: Follow the Tutorial Β· Read the Docs

πŸ’Ό Migration Guides

Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v2 to your site without starting from scratch!

❗ Code of Conduct

Gatsby is dedicated to building a welcoming, diverse, safe community. We expect everyone participating in the Gatsby community to abide by our Code of Conduct. Please read it. Please follow it. In the Gatsby community, we work hard to build each other up and create amazing things together. πŸ’ͺ πŸ’œ

🀝 How to Contribute

Whether you're helping us fix bugs, improve the docs, or spread the word, we'd love to have you as part of the Gatsby community! πŸ’ͺ πŸ’œ

Check out our Contributing Guide for ideas on contributing and setup steps for getting our repositories up and running on your local machine.

A note on how this repository is organized

This repository is a monorepo managed using Lerna. This means there are multiple packages managed in this codebase, even though we publish them to NPM as separate packages.

Contributing to Gatsby v1

We are currently only accepting bug fixes for Gatsby v1. No new features will be accepted.

πŸ“ License

Licensed under the MIT License.

πŸ’œ Thanks

Thanks to our many contributors and to Netlify for hosting Gatsby and our example sites.

GitHub

https://github.com/gatsbyjs/gatsby
Comments
  • 1. Error / page resources for / not found. Not rendering React

    Description

    I'm having multiple Bugsnag reports from Safari and Mobile Safari (various versions and browsers) of this error in .cache/production-app.js in publicLoader.loadPage:

    Capture d'écran 2019-11-19 12 20 44

    Steps to reproduce

    I don't see this Error in my macOS Safari. Website is https://lebikini.com

    Expected result

    No error

    Actual result

    An error

    Environment

    
      System:
        OS: macOS 10.14.6
        CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
        Shell: 5.3 - /bin/zsh
      Binaries:
        Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
        Yarn: 1.19.0 - /usr/local/bin/yarn
        npm: 6.12.0 - ~/.nvm/versions/node/v10.15.3/bin/npm
      Languages:
        Python: 2.7.16 - /usr/local/bin/python
      Browsers:
        Chrome: 78.0.3904.97
        Firefox: 70.0
        Safari: 13.0.3
      npmPackages:
        gatsby: ^2.17.13 => 2.17.13
        gatsby-image: ^2.2.32 => 2.2.32
        gatsby-plugin-google-analytics: ^2.1.26 => 2.1.26
        gatsby-plugin-manifest: ^2.2.27 => 2.2.27
        gatsby-plugin-netlify: ^2.1.24 => 2.1.24
        gatsby-plugin-react-helmet: ^3.1.14 => 3.1.14
        gatsby-plugin-sharp: ^2.2.38 => 2.2.38
        gatsby-plugin-styled-components: ^3.1.12 => 3.1.12
        gatsby-plugin-typescript: ^2.1.17 => 2.1.17
        gatsby-source-filesystem: ^2.1.36 => 2.1.36
        gatsby-transformer-sharp: ^2.3.4 => 2.3.4
    

    Related: https://github.com/gatsbyjs/gatsby/issues/15080

    Reviewed by antoinerousseau at 2019-11-19 11:27
  • 2. [gatsby-source-wordpress] Large WordPress site causing extremely slow build time (stuck at 'source and transform nodes')

    Description

    gatsby develop hangs on source and transform nodes after querying a large WordPress installation (~9000 posts, ~35 pages).

    Is there any guides as to what's too big for Gatsby to handle in this regards?

    Environment

      System:
        OS: macOS High Sierra 10.13.6
        CPU: x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
        Shell: 3.2.57 - /bin/bash
      Binaries:
        Node: 8.10.0 - ~/n/bin/node
        Yarn: 1.5.1 - ~/n/bin/yarn
        npm: 5.6.0 - ~/n/bin/npm
      Browsers:
        Chrome: 67.0.3396.99
        Safari: 11.1.2
      npmPackages:
        gatsby: ^1.9.273 => 1.9.273
        gatsby-image: ^1.0.54 => 1.0.54
        gatsby-link: ^1.6.45 => 1.6.45
        gatsby-plugin-google-analytics: ^1.0.27 => 1.0.31
        gatsby-plugin-postcss-sass: ^1.0.22 => 1.0.22
        gatsby-plugin-react-helmet: ^2.0.10 => 2.0.11
        gatsby-plugin-react-next: ^1.0.11 => 1.0.11
        gatsby-plugin-resolve-src: 1.1.3 => 1.1.3
        gatsby-plugin-sharp: ^1.6.48 => 1.6.48
        gatsby-plugin-svgr: ^1.0.1 => 1.0.1
        gatsby-source-filesystem: ^1.5.39 => 1.5.39
        gatsby-source-wordpress: ^2.0.93 => 2.0.93
        gatsby-transformer-sharp: ^1.6.27 => 1.6.27
      npmGlobalPackages:
        gatsby-cli: 1.1.58
    

    edit: Just want to reiterateβ€”this is not something easily fixable by deleted .cache/, .node_modules, etc. If that resolves your problem, you weren't experiencing this issue.

    Reviewed by dustinhorton at 2018-07-22 08:01
  • 3. [bug] β˜‚οΈ umbrella issue for schema customization issues

    This is a meta issue for all the issues with 2.2.0, that were introduced by the schema refactoring.

    What?

    See the blog post for the details about why we did the refactoring and what's it all about.

    See the release blog post for release notes and final updates.

    How?

    Install latest version of Gatsby and try running your site. Hopefully it will all just work. If you want, you could also try the two new APIs (createTypes and createResolvers).

    yarn add gatsby
    

    Changelog

    [email protected]

    • Published

    [email protected]

    • Moved to explicit directives instead of addResolver

    [email protected]

    • Master back merge, upgrade graphql-compose

    [email protected]

    • See #13028

    [email protected]

    • :champagne:

    [email protected]

    • Fixed a regression when empty strings mixed with dates cause stuff to not be intrepreted as dates

    [email protected]

    • merge latest master
    • docs update

    [email protected]

    • merge latest master
    • better SDL parse error messages

    [email protected]

    • fix regression in connection naming in case types are lowercase named

    [email protected]

    • Fixed custom scalars not having any filters
    • Added errors when trying to override Node interface or generated filter/sort types.

    [email protected]

    • Added a new convenience API modelled after graphql-compose. See using-type-definitions example.
    exports.sourceNodes = ({ actions, schema }) => {
      const { createTypes } = actions
      createTypes([
        schema.buildObjectType({
          name: `CommentJson`,
          fields: {
            text: `String!`,
            blog: {
              type: `BlogJson`,
              resolve(parent, args, context) {
                return context.nodeModel.getNodeById({
                  id: parent.author,
                  type: `BlogJson`,
                })
              },
            },
            author: {
              type: `AuthorJson`,
              resolve(parent, args, context) {
                return context.nodeModel.getNodeById({
                  id: parent.author,
                  type: `AuthorJson`,
                })
              },
            },
          },
          interfaces: [`Node`],
        }),
      ])
    }
    

    [email protected]

    • Fixed regression with Node id field not being a String, like in current master.
    • Upgraded to [email protected]
    • FilterInput types are now not prefixed by output type, reducing proliferation of types

    [email protected]

    • Fixed issue with pagination over null query results
    • @dontInfer(noDefaultResolvers: false) actually works
    • in createResolvers resolvers info.originalResolver is available even if there is no resolver on original field

    [email protected]

    • Redone alpha version with proper release version
    • Fix Node types without actual nodes not being added

    [email protected]

    • Initial alpha
    Reviewed by freiksenet at 2019-03-04 06:49
  • 4. Gatsby logo/branding

    Gatsby is awesome!

    Has been a while that I'm familiar with the project and I think it needs an equivalent awesome logo. Today I've seen this on Hacker News and I think it could be a nice spark for this discussion.

    @KyleAMathews do you have any ideas in mind?

    Reviewed by cusspvz at 2016-08-27 15:44
  • 5. Worse performance results with Lighthouse v6 (?)

    Just wondering whether there is some information that could be of use here, since I've found in my sites a significant worsening of lighthouse results when comparing lighthouse v5.6 vs the new 6.0 (https://lighthouse-metrics.com/)

    In a complex site (of mine) it goes (performance-wise) from a ~90 to ~50 In a simple starter (of mine) it lowers from ~98 to ~80

    This doesn't happen in starters such as https://gatsby-starter-default-demo.netlify.app/ or https://gatsby-v2-perf.netlify.app/

    But it does happen to www.gatsbyjs.org (from ~98 to ~73) or to https://theme-ui.com (from ~90 to ~75)

    Since I spent some time achieving 98-100 punctuations in my code (which made me very happy), I kind of feel I don't have a lot of room for improvement (probably I do have), so I've thought I might ask here if there's something going on

    Thanks

    Reviewed by kuworking at 2020-05-22 05:43
  • 6. gatsby-plugin-react-helmet orders the components too late in

    Description

    When I use gatsby-plugin-react-helmet I notice that the <Helmet /> components come way too late in the head tag. I have noticed that on occasion for instance Facebook does not always parse the og tags if they come too late in the head.

    Steps to reproduce

    Just use <Helmet />, and notice in the static output files there is a lot of CSS related stuff etc. above the helmet tag in the <head>.

    Expected result

    Helmet tags should be prioritised when doing the <head /> tag.

    Workaround

    Currently there is easy workaround, but I consider that gatsby's default is broken. We should not need workaround for this.

    gatsby-ssr.js

    var React = require("react");
    
    // Hack, to reorder the helmet components as first in <head> tag
    exports.onPreRenderHTML = ({ getHeadComponents, replaceHeadComponents }) => {
        /**
         * @type {any[]} headComponents
         */
        const headComponents = getHeadComponents();
    
        headComponents.sort((a, b) => {
            if (a.props && a.props["data-react-helmet"]) {
                return 0;
            }
            return 1;
        });
        replaceHeadComponents(headComponents);
    };
    
    Reviewed by Ciantic at 2020-03-12 14:17
  • 7. [gatsby-plugin-offline] [gatsby/cache-dir] Fix various offline and caching issues

    Changes made:

    • <div> is replaced with <span> in gatsby-plugin-offline's app-shell.js to prevent an edge case in Chrome, where the the outer element's class attribute is unset despite its className being set in the VDOM, if the page was loaded from the offline shell.
    • A call to getResourcesForPathname was fixed - previously this prevented later code from calling since Promise.all(pathnameResources) would never resolve.
    • Styles are now searched as well as scripts when caching resources, and these are all cached regardless of whether they are included in pageResources.
    • Styles are also now searched in get-resources-from-html.js.
    • The offline shell and custom 404 page are now also scanned for resources when considering critical file paths.
      • get-resources-from-html.js is modified so that if a custom 404 page doesn't exist, an empty array will be returned.
    • A glob for Webpack chunks is added to the precache options, as these are sometimes loaded from other chunks and therefore not detected by getResourcesFromHTML, causing errors to occur when trying to navigate to another page when offline (if they haven't all been cached).
    • The navigateFallbackWhitelist regex is modified to prevent loading the offline shell if the URL ends with ?no-cache=1 or &no-cache=1.
    • sw.js is patched to include search queries when matching URLs against navigateFallbackWhitelist. Unfortunately I couldn't find any options to enable this, so patching appears to be the only way until a change is made upstream.
      • An error is thrown asking the user to report an issue if the patch fails - this will cause the build to fail, but will avoid confusion in the long run if the patch stops working.
      • I checked the ignoreUrlParametersMatching options, but it's for ignoring differences, e.g. between /page/ and /page/?utm_source=github, not for disabling caching or fallback.
    • JSON and CSS resources are cached at runtime.
    • page-renderer.js now checks for this.state.pageResources.json, since errors were previously occurring even when this.state.pageResources existed due to the missing JSON data.
    • When a page isn't found, an attempt is made to load it directly, in order to display a proper error message, i.e. 404 or offline error, or simply load it directly if it's available online (e.g. /admin/ for CMS, which is not directly part of Gatsby).
    • A clause has been added to an if statement in production-app.js to prevent the 404 showing until an attempt has been made to load the page directly
      • #7268 had actually broken support for static pages (e.g. Netlify CMS at /admin/) since the service worker would be unable to find the page from Gatsby and show a 404
    • onServiceWorkerInstalled is now delayed by 100ms, since it was being called before the fetch event listeners were added, thus preventing resources from being cached. Unfortunately I couldn't find a programmatic way to do this (other than more patching of sw.js, which is less than ideal).
      • It might be worth increasing this to 500ms, since at 100ms it could still fail for more complex sites (despite working at as low as 20ms in local testing). Thoughts?
    • checkIfDoingInitialRenderForSW is removed from loader.js as it was causing the SW to be removed when navigating to a nonexistent page, even if the website had not been updated, causing it to stop working offline entirely - regardless, it is no longer needed with the other changes made.
    • README for gatsby-plugin-offline is updated to match the latest default options.

    Closes #6212, Closes #7053, Closes #6688, possibly others

    Reviewed by valerie-makes at 2018-08-15 17:13
  • 8. Missing resources for /

    Summary

    Periodically on my production site I'm seeing the following error;

    Error: Missing resources for /
      at render(./.cache/ensure-resources.js:133:17)
      at Sg(./node_modules/react-dom/cjs/react-dom.production.min.js:169:129)
      at Hh(./node_modules/react-dom/cjs/react-dom.production.min.js:214:16)
      at Ih(./node_modules/react-dom/cjs/react-dom.production.min.js:215:274)
      at ji(./node_modules/react-dom/cjs/react-dom.production.min.js:230:233)
      at ki(./node_modules/react-dom/cjs/react-dom.production.min.js:229:143)
      at Fh(./node_modules/react-dom/cjs/react-dom.production.min.js:226:196)
      at bg(./node_modules/react-dom/cjs/react-dom.production.min.js:224:28)
      at qi(./node_modules/react-dom/cjs/react-dom.production.min.js:243:14)
      at render(./node_modules/react-dom/cjs/react-dom.production.min.js:251:109)
      at oi(./node_modules/react-dom/cjs/react-dom.production.min.js:254:364)
      at Ai(./node_modules/react-dom/cjs/react-dom.production.min.js:254:350)
      at apply(./.cache/production-app.js:114:7)
      at r(./node_modules/@sentry/browser/dist/index.js:3114:1)
    

    It seems like sometimes this causes the site to not render at all and just show a blank page.

    Relevant information

    You can see the trace on Sentry here

    Environment (if relevant)

    This is the env on which the site is built;

      System:
        OS: macOS High Sierra 10.13.2
        CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
        Shell: 5.3 - /bin/zsh
      Binaries:
        Node: 8.11.1 - ~/.nvm/versions/node/v8.11.1/bin/node
        Yarn: 1.9.4 - ~/.nvm/versions/node/v8.11.1/bin/yarn
        npm: 6.4.1 - ~/.nvm/versions/node/v8.11.1/bin/npm
      Browsers:
        Chrome: 71.0.3578.98
        Safari: 11.0.2
      npmPackages:
        gatsby: ^2.0.19 => 2.0.72
        gatsby-image: ^2.0.15 => 2.0.20
        gatsby-plugin-create-client-paths: ^2.0.2 => 2.0.2
        gatsby-plugin-google-gtag: ^1.0.8 => 1.0.8
        gatsby-plugin-manifest: ^2.0.5 => 2.0.10
        gatsby-plugin-offline: ^2.0.11 => 2.0.17
        gatsby-plugin-page-transitions: ^1.0.7 => 1.0.7
        gatsby-plugin-react-helmet: ^3.0.0 => 3.0.2
        gatsby-plugin-sharp: ^2.0.18 => 2.0.18
        gatsby-plugin-stripe-elements: ^1.0.9 => 1.0.9
        gatsby-plugin-twitter: ^2.0.8 => 2.0.8
        gatsby-source-filesystem: ^2.0.4 => 2.0.12
        gatsby-transformer-sharp: ^2.1.12 => 2.1.12
      npmGlobalPackages:
        gatsby-cli: 2.0.0-rc.1
        gatsby-plugin-countly: 0.2.0
    

    No idea where to start with debugging this so any help is appreciated!

    Reviewed by Jivings at 2019-02-03 16:30
  • 9. error UNHANDLED EXCEPTION write EPIPE while running on Netlify

    Preliminary Checks

    • [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
    • [X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

    Description

    When trying to run Gatsby latest 4.9.1 I get this error

    4:35:23 PM: success write out requires - 0.005s
    4:36:27 PM: success Building production JavaScript and CSS bundles - 63.377s
    4:37:03 PM: success Building HTML renderer - 36.060s
    4:37:03 PM: success Execute page configs - 0.380s
    4:37:03 PM: success Caching Webpack compilations - 0.001s
    4:37:03 PM: error (node:2227) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added to [PassThrough]. Use emitter.setMaxListeners() to increase limit
    4:37:03 PM: (Use `node --trace-warnings ...` to show where the warning was created)
    4:37:07 PM: success run queries in workers - 3.599s - 37/37 10.28/s
    4:37:09 PM: success Running gatsby-plugin-sharp.IMAGE_PROCESSING jobs - 120.528s - 5/5 0.04/s
    4:37:09 PM: error UNHANDLED EXCEPTION write EPIPE
    4:37:09 PM: 
    4:37:09 PM: 
    4:37:09 PM:   Error: write EPIPE
    4:37:09 PM:   
    4:37:09 PM:   - child_process:864 ChildProcess.target._send
    4:37:09 PM:     node:internal/child_process:864:20
    4:37:09 PM:   
    4:37:09 PM:   - child_process:737 ChildProcess.target.send
    4:37:09 PM:     node:internal/child_process:737:19
    4:37:09 PM:   
    4:37:09 PM:   - index.js:291 WorkerPool.sendMessage
    4:37:09 PM:     [repo]/[gatsby-worker]/dist/index.js:291:19
    4:37:09 PM:   
    4:37:09 PM:   - worker-messaging.ts:22 
    4:37:09 PM:     [repo]/[gatsby]/src/utils/jobs/worker-messaging.ts:22:22
    4:37:09 PM:   
    4:37:09 PM: 
    4:37:09 PM: not finished Merge worker state - 0.058s
    4:37:09 PM: error Command failed with exit code 1.
    4:37:09 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
    4:37:09 PM: ​
    4:37:09 PM: ────────────────────────────────────────────────────────────────
    4:37:09 PM:   "build.command" failed                                        
    4:37:09 PM: ────────────────────────────────────────────────────────────────
    4:37:09 PM: ​
    4:37:09 PM:   Error message
    4:37:09 PM:   Command failed with exit code 1: yarn postinstall && yarn build:incremental
    4:37:09 PM: ​
    4:37:09 PM:   Error location
    4:37:09 PM:   In build.command from netlify.toml:
    4:37:09 PM:   yarn postinstall && yarn build:incremental
    4:37:09 PM:
    

    I cleared my Netlify cache before running this and this seems like a new issue as per https://github.com/gatsbyjs/gatsby/issues/33738#issuecomment-1055595579

    Reproduction Link

    tbd

    Steps to Reproduce

    Following steps outlined here: https://github.com/gatsbyjs/gatsby/issues/33738

    Expected Result

    For the site to build as it normally did before I updated packages.

    Actual Result

    Consistently fails

    Environment

    System:
        OS: macOS 12.0.1
        CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
        Shell: 5.8 - /bin/zsh
      Binaries:
        Node: 17.4.0 - /var/folders/tb/qb7x5sw53vngt06y9g92csn80000gp/T/yarn--1646432031346-0.9788514151471666/node
        Yarn: 1.22.17 - /var/folders/tb/qb7x5sw53vngt06y9g92csn80000gp/T/yarn--1646432031346-0.9788514151471666/yarn
        npm: 8.3.1 - ~/.nvm/versions/node/v17.4.0/bin/npm
      Languages:
        Python: 2.7.18 - /usr/bin/python
      Browsers:
        Chrome: 99.0.4844.51
        Safari: 15.1
    

    Config Flags

    GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true

    Links/References

    https://answers.netlify.com/t/error-unhandled-exception-write-epipe/52650 https://answers.netlify.com/t/gatsby-v4-works-locally-but-timed-out-on-netlify/46339/2 https://answers.netlify.com/t/gatsby-v4-works-locally-but-timed-out-on-netlify/46339/21

    Reviewed by wahidshafique at 2022-03-04 22:14
  • 10. Errors when processing large(ish) numbers of images with gatsby-plugin-sharp

    Description

    I'm processing around 1500 images with gatsby-plugin-sharp/gatsby-transformer-sharp and GraphQL, to display with gatsby-image as per this page in the docs.

    For smaller numbers of images I have had no issues, but now that I'm processing 1500 images the build randomly fails with the following error:

    (sharp:104): GLib-GObject-WARNING **: 09:35:11.293: gtype.c:4265: type id '0' is invalid
    
    (sharp:104): GLib-GObject-WARNING **: 09:35:11.293: can't peek value table for type '<invalid>' which is not currently referenced
    
    (sharp:104): GLib-GObject-WARNING **: 09:35:11.293: gvalue.c:188: cannot initialize GValue with type '(null)', this type has no GTypeValueTable implementation
    
    (sharp:104): GLib-GObject-CRITICAL **: 09:35:11.293: g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
    Received 'segmentation fault' signal
    

    This happens during the "Generating image thumbnails" step in the build process and it occurs apparently randomly (sometimes 10% of the way through the images, sometimes at 80%, sometimes not at all). Therefore I do not believe it is caused by a "faulty image".

    Reviewed by jp887 at 2018-07-04 10:55
  • 11. Gatsby t-shirt design contest

    Who wants to design a Gatsby t-shirt!?!

    We have $1240 available on OpenCollective that seems like it needs turned into t-shirts :-)

    But to do that we need a design. So please submit some designs! If you submit the design that gets picked, I'll send you 3 t-shirts.

    I'm also going to send t-shirts to all the 1.0 contributors.

    What's the best t-shirt printing place these days? Ideally they'd be a print on-demand place so people could buy Gatsby shirts for themselves.

    Reviewed by KyleAMathews at 2017-07-13 22:47
  • 12. fix(gatsby-cli): Set `NODE_ENV` earlier in commandHandler

    Description

    The reproduction in https://github.com/gatsbyjs/gatsby/issues/35018 showed that the main process and query workers were using different LMDB files. It showed that the main process used the test file:

    https://github.com/gatsbyjs/gatsby/blob/db682079e722f0ac1214be917d7bc24d4f6a847a/packages/gatsby/src/utils/cache-lmdb.ts#L5-L14

    And the workers the correct LMDB files.

    This PR moves the process.env.NODE_ENV call to before we require gatsby (and initiate LMDB).

    Related Issues

    Fixes https://github.com/gatsbyjs/gatsby/issues/35018 [ch52019]

    Reviewed by LekoArts at 2022-06-21 13:09
  • 13. fix(deps): update starters and examples - gatsby

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | gatsby (changelog) | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-plugin-feed | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-plugin-gatsby-cloud | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-plugin-google-analytics | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-plugin-image | ^2.16.1 -> ^2.17.0 | age | adoption | passing | confidence | | gatsby-plugin-manifest | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-plugin-offline | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-plugin-react-helmet | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-plugin-sharp | ^4.16.1 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-remark-copy-linked-files | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-remark-images | ^6.16.0 -> ^6.17.0 | age | adoption | passing | confidence | | gatsby-remark-prismjs | ^6.16.0 -> ^6.17.0 | age | adoption | passing | confidence | | gatsby-remark-responsive-iframe | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-remark-smartypants | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-source-filesystem | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence | | gatsby-source-wordpress | ^6.16.1 -> ^6.17.0 | age | adoption | passing | confidence | | gatsby-transformer-remark | ^5.16.0 -> ^5.17.0 | age | adoption | passing | confidence | | gatsby-transformer-sharp | ^4.16.0 -> ^4.17.0 | age | adoption | passing | confidence |


    Release Notes

    gatsbyjs/gatsby (gatsby)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-feed)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-gatsby-cloud)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-google-analytics)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-image)

    v2.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-manifest)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-offline)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-react-helmet)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-plugin-sharp)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-remark-copy-linked-files)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-remark-images)

    v6.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-remark-prismjs)

    v6.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-remark-responsive-iframe)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-remark-smartypants)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-source-filesystem)

    v4.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-source-wordpress)

    v6.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-transformer-remark)

    v5.17.0

    Compare Source

    gatsbyjs/gatsby (gatsby-transformer-sharp)

    v4.17.0

    Compare Source


    Configuration

    πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

    🚦 Automerge: Enabled.

    β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    πŸ‘» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by Mend Renovate. View repository job log here.

    Reviewed by renovate[bot] at 2022-06-21 13:04
  • 14. feat(gatsby): `typesOutputPath` option for `graphqlTypegen`

    Description

    Makes the output of the TS definitions file configurable. The PR is already written in a way to allow future additions to these options.

    Feature Request: https://github.com/gatsbyjs/gatsby/discussions/35779

    Documentation

    The relevant documentation was updated.

    Related Issues

    [ch51305] https://github.com/gatsbyjs/gatsby/discussions/35779

    Reviewed by LekoArts at 2022-06-21 10:26
  • 15. feat(gatsby): Metadata management

    Description

    Link to RFC

    Todo

    • [ ] Warnings and descriptive error messages
    • [ ] End-to-end tests
    • [ ] Unit tests

    Documentation

    This will go into a separate PR before release

    Reviewed by marvinjude at 2022-06-20 11:23
  • 16. chore(deps): update starters and examples

    Mend Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | @types/node | ^17.0.42 -> ^17.0.45 | age | adoption | passing | confidence | | @types/react | ^18.0.12 -> ^18.0.14 | age | adoption | passing | confidence | | prettier (source) | ^2.6.2 -> ^2.7.1 | age | adoption | passing | confidence | | theme-ui | 0.14.5 -> 0.14.6 | age | adoption | passing | confidence | | typescript (source) | ^4.7.3 -> ^4.7.4 | age | adoption | passing | confidence |


    Release Notes

    prettier/prettier

    v2.7.1

    Compare Source

    diff

    Keep useful empty lines in description (#​13013 by @​chimurai)

    v2.7.0

    Compare Source

    """ First line Second Line """ type Person { name: String }

    system-ui/theme-ui

    v0.14.6

    Compare Source

    πŸ› Bug Fix
    • @theme-ui/prism
    Authors: 1
    Microsoft/TypeScript

    v4.7.4

    Compare Source

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:


    Configuration

    πŸ“… Schedule: Branch creation - "before 7am on Monday" in timezone GMT, Automerge - At any time (no schedule defined).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    πŸ‘» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


    • [ ] If you want to rebase/retry this PR, click this checkbox.

    This PR has been generated by Mend Renovate. View repository job log here.

    Reviewed by renovate[bot] at 2022-06-20 02:11
🌟 DataFormsJS 🌟 A minimal JavaScript Framework, standalone React and Web Components, and JSX Compiler for rapid development of high quality websites and single page applications.
🌟 DataFormsJS 🌟 A minimal JavaScript Framework, standalone React and Web Components, and JSX Compiler for rapid development of high quality websites and single page applications.

?? DataFormsJS ?? A minimal JavaScript Framework, standalone React and Web Components, and JSX Compiler for rapid development of high quality websites and single page applications.

Jun 13, 2022
A data-driven, functional, and reactive framework for building Modern Web Apps in JavaScript.
A data-driven, functional, and reactive framework for building Modern Web Apps in JavaScript.

A data-driven, functional, and reactive framework for building Modern Web Apps in JavaScript. It leverages React, inspired by re-frame.

Mar 2, 2022
A framework that let's you compose websites in Python with ease!

Perry Perry <= A framework that let's you compose websites in Python with ease! Perry works similar to Qt and Flutter, allowing you to create componen

Jan 18, 2022
web3-react🧰 A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

?? A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

Jun 24, 2022
🧰 A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

?? A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

Jun 23, 2022
A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps

Nov 1, 2021
Astrodon - Make Desktop apps with Deno πŸ¦•

?? Astrodon Desktop App Framework (not there yet!) for Deno, based on Tauri ?? Features Create webview windows with your own title and URL Bidirection

Jun 18, 2022
Estrela a Javascript framework to develop reactive web apps
Estrela  a Javascript framework to develop reactive web apps

Estrela - Full Reactive Framework Estrela is a Javascript framework to develop reactive web apps. Estrela is extremely easy to use, all the hard work

Jun 15, 2022
Create a SPA project using Mithril JS framework and design layout by JSX syntax and use Typescript and Vite for build system.
Create a SPA project using Mithril JS framework and design layout by JSX syntax and use Typescript and Vite for build system.

Mithril TS(Type script) JSX Create a SPA project using Mithril JS framework and design layout by JSX syntax and use Typescript and Vite for build syst

Feb 22, 2022
Datapod for React - a framework which extends create-react-app to enables you to quickly build data-driven sites
Datapod for React - a framework which extends create-react-app to enables you to quickly build data-driven sites

This is a framework which extends create-react-app to enables you to quickly build data-driven sites. This code is generated from the Datapod-for-React Core application.

Mar 19, 2022
Use React in Vue3 and Vue3 in React, And as perfect as possible
Use React in Vue3 and Vue3 in React, And as perfect as possible

Veaury (pronounced /ˈvjuːri/, inspired by 'beauty') is a tool library. It is built on the Vue and React framework. It's use cases include using both Vue and React in one app, migrating from React to Vue or from Vue to React

Jun 20, 2022
A frontend Framework for building B2B applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Material Design
A frontend Framework for building B2B applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Material Design

react-admin A frontend Framework for building data-driven applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Materi

Jun 26, 2022
The Full-stack Framework for React and other in Deno.

The Full-stack Framework for React and other in Deno.

Jun 17, 2022
πŸ›‘οΈ βš›οΈ A simple, scalable, and powerful architecture for building production ready React applications.

??️ βš›οΈ A simple, scalable, and powerful architecture for building production ready React applications.

Jun 21, 2022
Declarative data-fetching and caching framework for REST APIs with React
Declarative data-fetching and caching framework for REST APIs with React

Declarative data-fetching and caching framework for REST APIs with React

Jun 12, 2022
A declarative, efficient, and flexible JavaScript library for building user interfaces.

React Β· React is a JavaScript library for building user interfaces. Declarative: React makes it painless to create interactive UIs. Design simple view

Jun 20, 2022
A system combining classical traces dumping tools and a ReactJS web app for live 3D graph rendering of streamed graph data derived from traces
A system combining classical traces dumping tools and a ReactJS web app for live 3D graph rendering of streamed graph data derived from traces

The DynaGraph framework: a system combining classical traces dumping tools (i.e. the tshark tool and Firefox's Network Monitor component) and a ReactJS web app for live 3D graph rendering of streamed graph data derived from traces

Apr 28, 2022
A light-weight, comprehensive, reactive framework for business logic and when things change.

watchlight.dev v1.0.15 beta << For when things change. A light-weight, comprehensive, reactive framework for business logic and when things change. In

May 13, 2022