Upgrade -core and -docs from Gatsby v2

lorensr commented 3 years ago

There are a list of compatibility warnings when updating the docs to v3:

warn Plugin gatsby-theme-apollo-core is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.13.80
warn Plugin gatsby-theme-apollo-docs is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.13.80

as well as a lot of packages used by the two themes.

Edit: v4 is out! https://v4.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/

mrlubos commented 3 years ago

I am also running into issues when trying to integrate with the latest version of Gatsby

DirkLachowski commented 3 years ago

Is there a timeline for that? Using v3 crashes with

Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
 - configuration.module.rules[11] should be one of these:
   ["..." | object { compiler?, dependency?, descriptionData?, enforce?, exclude?, generator?, include?, issuer?, issuerLayer?, layer?, loader?, mimetype?, oneOf?, options?, parser?, realResource?, resolve?, resource?, resourceFragment?, resourceQuery?, rules?, scheme?, sideEffects?, test?, type?, use? }, ...]
   -> A rule.
   Details:
    * configuration.module.rules[10].issuer has an unknown property 'test'. These properties are valid:
      object { and?, not?, or? }
      -> Logic operators used in a condition matcher.
    * configuration.module.rules[11].issuer has an unknown property 'test'. These properties are valid:
      object { and?, not?, or? }
      -> Logic operators used in a condition matcher.

as described here: https://github.com/apollographql/apollo/issues/1157#issuecomment-851779782