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

Dependency resolution fails using Node 18 LTS #10

Open
leifwritescode opened this issue Dec 25, 2022 · 1 comment
Open

Dependency resolution fails using Node 18 LTS #10

leifwritescode opened this issue Dec 25, 2022 · 1 comment

Comments

@leifwritescode
Copy link

Using the instructions in the readme, it is not possible to initialise this starter using gatsby new. The following errors are seen.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: gatsby-attila-theme-starter@1.0.0
npm ERR! Found: gatsby@2.20.24
npm ERR! node_modules/gatsby
npm ERR!   dev gatsby@"2.20.24" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^4.13.1" from gatsby-plugin-mixpanel@3.7.0
npm ERR! node_modules/gatsby-plugin-mixpanel
npm ERR!   gatsby-plugin-mixpanel@"^3.1.6" 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.

Using WSL2 on Windows 11, with Ubuntu 22.04. Bare install with python2 and build-essential.

@leifwritescode
Copy link
Author

Switching to Node v14 latest and using gatsby-cli@4.13.0 gets you past the gatsby new stage, but then gatsby develop fails when pointed at a Ghost v5 CMS. The absence of prerequisite information makes this starter very difficult to use.

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

1 participant