[Bug/build] Conflicting versions of eslint breaks build

[jamecoyne]

Hi,

I encountered a strange issue when trying to build a new version of my personal site built with this theme on Gitlab where I merged a commit that only changed the markdown content of one page.

In essence, it seems if I'm understanding correctly there's a conflict between versions of eslint that the theme uses and the eslint that gatsby uses?

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: gatsby-starter-amsterdam@2.0.1
npm ERR! Found: eslint@8.23.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.23.0" from eslint-config-gatsby-standard@3.0.2
npm ERR! node_modules/eslint-config-gatsby-standard
npm ERR!   dev eslint-config-gatsby-standard@"^3.0.2" 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! 

Not sure if I'm understanding this correctly.

Since then I've tried.

• upgrading all packages
• uninstalling gatsby + all dependencies completely, re-installinng the project
• uninstalling gatsby + all dependencies completely, creating a new project with the theme
• creating a new gatsby project, manually adding the theme.

All roads seem to lead to this error, and I'm not sure what I'm doing wrong here - any advice would be very much appreciated.

[meninoebom]

I'm having the same issue.

[jamecoyne]

woo, glad I'm not the only one having that issue. I'll ping a friend with more experience with build issues and let you know if we find a solution.

[spolanski]

Anyone managed to solve the issue? I am experiencing the same thing