nickymeuleman / gatsby-plugin-extract-schema Goto Github PK

Hi, you should write schema to file only if schema has changed to avoid unnecessary runs from other programs watching it.

After updating to Gatsby v3, schema.json wasn't being created any longer. After a little digging, it looks like const { introspectionQuery, graphql } = require("gatsby/graphql"); is referencing a string that is no longer being exported from 'gatsby/graphql'.

Looking closer at graphql.js, { GraphQLJSON } no longer contains introspectionQuery in the latest version of graphql-compose

I receive this error when upgrading. Is it worth just replacing the usages of ?? with || (if falsey check is applicable) to avoid any compiler issues?

  Error:[..]node_modules/gatsby-plugin-extract-schema/gatsby-node.js:13
      const location = options.dest ?? defaultLocation;
                                     ^
  SyntaxError: Unexpected token '?'

Edit: forgot to mention I tried the suggested addition of babel-preset-gatsby in babel config, but that did not help.

Right now the schema is not stable, so everytime it runs a new schema is generated. This is an issue when you'd like to check it in in source control.

A solution would be to sort the arrays in the schema.

This could be as simple as updating peerDependencies to `"gatsby": "^2.0.0 || ^3.0.0 || ^4.0.0".

I haven't tested extensively, but it seems to work fine on my sites after migration to v4, but there's a complaint from both npm and the gatsby build that this plugin doesn't support gatsby 4.

Just opening an issue to go with my pull request #11. Basically the same fix as #9, and I've had no problems.