gatsby-plugin-intl icon indicating copy to clipboard operation
gatsby-plugin-intl copied to clipboard

Is this plugin going to be updated to supported gatsby version 4.x.x?

Open gtupak opened this issue 3 years ago • 1 comments

Every time I run gatsby develop, I get the following: Plugin gatsby-plugin-intl is not compatible with your gatsby version 4.9.3 - It requires gatsby@^2.0.0

gtupak avatar Mar 13 '22 02:03 gtupak

I believe it is compatible functionally and that is just a standard semver warning.

graysonhicks avatar Jun 16 '22 19:06 graysonhicks

I've also been working on an alternative for a while: https://github.com/openscript-ch/gatsby-plugin-i18n-l10n

openscript avatar Oct 02 '22 15:10 openscript

Can confirm that the plugin is working as intended, but every time I try to run npm install I get an error that prevents installation:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"5.5.0" from the root project
npm ERR!   peer gatsby@"^5.0.0-next" from [email protected]
npm ERR!   node_modules/babel-plugin-remove-graphql-queries
npm ERR!     babel-plugin-remove-graphql-queries@"^5.5.0" from [email protected]
npm ERR!     babel-plugin-remove-graphql-queries@"^5.5.0" from [email protected]
npm ERR!     node_modules/gatsby-plugin-typescript
npm ERR!       gatsby-plugin-typescript@"^5.5.0" from [email protected]
npm ERR!   15 more (gatsby-plugin-google-gtag, gatsby-plugin-manifest, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^2.0.0" from [email protected]
npm ERR! node_modules/gatsby-plugin-intl
npm ERR!   gatsby-plugin-intl@"0.3.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   peer gatsby@"^2.0.0" from [email protected]
npm ERR!   node_modules/gatsby-plugin-intl
npm ERR!     gatsby-plugin-intl@"0.3.3" from the root project

Tested on Gatsby 5

whyboris avatar Feb 01 '23 04:02 whyboris

@whyboris With Gatsby 5 in general (because of React 18) you will want to install with --legacy-peer-deps or a package manager that does that automatically.

graysonhicks avatar Feb 02 '23 18:02 graysonhicks

🤝 thank you -- that's what I have to resort to 😅 ... but it would be pretty easy to just change the version number in this repository's packages.json and the problem would be solved, right?

https://github.com/wiziple/gatsby-plugin-intl/blob/master/package.json#L38

whyboris avatar Feb 02 '23 18:02 whyboris

@wiziple - thank you for this very useful plugin 🙇 If I create a PR updating the package.json peerDependencies to Gatsby version 5, would you be willing to merge it in and create a new npm release? 😊

It seems like the plugin works perfectly (I'm using it for Health Impact Fund), it's just that we all get a needless error when trying to npm install and have to resort to npm install --legacy-peer-deps 😅

whyboris avatar Feb 04 '23 21:02 whyboris

There's already a PR for Gatsby 3 😅 #173 🚀

whyboris avatar Feb 04 '23 21:02 whyboris