-
Notifications
You must be signed in to change notification settings - Fork 424
docs: consider updating to gatsby 3 #1157
Comments
This would fix #1164. When I update this repo to Gatsby v3, I get these errors (after switching to minimum Node 12):
warn Plugin gatsby-plugin-emotion is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-plugin-react-helmet is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-plugin-less is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
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-source-filesystem is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.2.0
warn Plugin gatsby-transformer-remark is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.12.0
warn Plugin gatsby-plugin-google-gtag is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-theme-apollo-docs is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.13.80
warn Plugin gatsby-remark-autolink-headers is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-remark-copy-linked-files is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-remark-prismjs is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-plugin-emotion is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-plugin-react-helmet is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-plugin-less is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
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-source-filesystem is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.2.0
warn Plugin gatsby-remark-autolink-headers is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-remark-copy-linked-files is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-remark-prismjs is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-transformer-remark is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.12.0
warn Plugin gatsby-plugin-google-gtag is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.0.0
warn Plugin gatsby-theme-apollo-docs is not compatible with your gatsby version 3.6.1 - It requires gatsby@^2.13.80
success load plugins - 1.605s
success onPreInit - 0.035s
success initialize cache - 0.009s
success copy gatsby files - 0.121s
success onPreBootstrap - 0.021s
success createSchemaCustomization - 0.257s
warn code block or inline code language not specified in markdown. applying generic code block
success Checking for changed pages - 0.002s
success source and transform nodes - 3.027s
success building schema - 0.472s
success createPages - 0.087s
success createPagesStatefully - 0.053s
info Total nodes: 178, SitePage nodes: 23 (use --verbose for breakdown)
success Checking for changed pages - 0.001s
success update schema - 0.087s
success write out redirect data - 0.001s
success onPostBootstrap - 0.001s
info bootstrap finished - 9.019s
success onPreExtractQueries - 0.001s
success extract queries from components - 0.396s
success write out requires - 0.007s
success run static queries - 0.014s - 2/2 146.14/s
success run page queries - 0.685s - 3/3 4.38/s
ERROR Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
|
Gatsby 2 has exited its maintenance window and is only receiving critical security updates - I imagine we'd want to update across each of the different netlify docsets across apollo, but it's quite possible we could do these updates piece by piece.
For quick reference, the migration guide can be found here
The text was updated successfully, but these errors were encountered: