Gatsby v5

[emiliekmartinez]

Description

Gatsby has upgraded to v5, and this plugin isn't compatible:

warn Plugin gatsby-plugin-next-seo is not compatible with your gatsby version 5.0.1 - It requires gatsby@^2.0.0 || ^3.0.0 || ^4.0.0

Checklist

• [x] I have read the contributing document.

[Vacilando]

Same here:

warn Plugin gatsby-plugin-next-seo is not compatible with your gatsby version 5.2.0 - It requires gatsby@^2.0.0 || ^3.0.0 || ^4.0.0

[jdortegar]

Same here :(

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: webstore@5.0.0
npm ERR! Found: gatsby@5.9.0
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"^5.9.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^2.0.0 || ^3.0.0 || ^4.0.0" from gatsby-plugin-next-seo@1.10.0
npm ERR! node_modules/gatsby-plugin-next-seo
npm ERR!   gatsby-plugin-next-seo@"^1.10.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /Users/jdortega/.npm/_logs/2023-05-03T16_25_40_460Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jdortega/.npm/_logs/2023-05-03T16_25_40_460Z-debug-0.log

[eliasblume]

Same issue here ...

[MohdSohail]

Same here -

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: gatsby-starter-default@0.1.0
npm ERR! Found: gatsby@5.11.0
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"^5.10.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^2.0.0 || ^3.0.0 || ^4.0.0" from gatsby-plugin-next-seo@1.10.0
npm ERR! node_modules/gatsby-plugin-next-seo
npm ERR!   gatsby-plugin-next-seo@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

It looks like the package has been abandoned.

For those who're wondering if it'll work with Gatsby 5.0 upon force installing it, well, I had a project last year in Gatsby 4. with gatsby-plugin-next-seo installed, and I upgraded gatsby to 5.0. Everything continued to work properly. But it's before other gatsby's major and minor updates, I don't know if it'll work seamlessly now with Gatsby 5.11..

[ifiokjr]

I'm open to all pull requests 👍