Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade peer-deps to include gatsby 5.x #106

Open
NicolasdRa opened this issue Jan 20, 2023 · 2 comments
Open

Upgrade peer-deps to include gatsby 5.x #106

NicolasdRa opened this issue Jan 20, 2023 · 2 comments

Comments

@NicolasdRa
Copy link

image

@skoch
Copy link

skoch commented Mar 28, 2023

❯ yarn start
yarn run v1.22.19
$ gatsby develop
success compile gatsby files - 0.603s
success load gatsby config - 0.017s
warn Plugin gatsby-theme-material-ui-top-layout is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
warn Plugin gatsby-plugin-material-ui is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
warn Plugin gatsby-theme-material-ui is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
warn Plugin gatsby-theme-material-ui-top-layout is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
warn Plugin gatsby-plugin-material-ui is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
warn Plugin gatsby-theme-material-ui is not compatible with your gatsby version 5.8.0 - It requires gatsby@^3.0.0 || ^4.0.0
success load plugins - 0.161s
success onPreInit - 0.003s

Any plans to update peerDependencies.gatsby for these to include current Gatsby?

eg: https://github.com/hupe1980/gatsby-theme-material-ui/blob/master/packages/gatsby-theme-material-ui/package.json#L30

@codytodonnell
Copy link

For anyone who needs a workaround, I currently use:

npm install --legacy-peer-deps

It would be great if the peer dependencies could be updated to support gatsby 5.x. I have been using this library with gatsby 5.12.4 using the --legacy-peer-deps workaround and I have not run into any major issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants