Default settings compatibility issue: eslint-plugin-n

[JosephBarkate]

Describe the bug

Installing the boilerplate with: npx ignite-cli@latest new PizzaApp, and accepting all the default settings leads to a compatibility issue while doing my first npm install.

The error:
git:(main) ✗ npm install 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/eslint-plugin-n npm ERR! dev eslint-plugin-n@"^17.10.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer eslint-plugin-n@"^15.0.0 || ^16.0.0 " from [email protected] npm ERR! node_modules/eslint-config-standard npm ERR! dev eslint-config-standard@"^17.1.0" from the root project

The Solution:
Not ideal but to get around this I downgraded two package versions and my boilerplate seems to be installing correctly now. These are the two packages I had to downgrade 1 major version:

"eslint-plugin-n": "^16.0.0", "eslint-plugin-promise": "^6.0.0",

Not sure if this will eventually be fixed upstream or if its requires a PR, but would appreciate a second opinion. Thanks again for providing this product!

Ignite version

release

Additional info

System
  platform           darwin                                              
  arch               arm64                                               
  cpu                12 cores      Apple M3 Pro                          
  directory          neighborrow   /Users/jbarkate/workspace/neighborrow 

JavaScript (and globally-installed packages)
  node               21.6.1       /Users/jbarkate/.nvm/versions/node/v21.6.1/bin/node 
  npm                10.2.4       /Users/jbarkate/.nvm/versions/node/v21.6.1/bin/npm  
    corepack         0.24.0                                                           
    eas-cli          14.0.2                                                           
    npm              10.2.4                                                           
  yarn               -            not installed                                       
  pnpm               -            not installed                                       
  bun                -            not installed                                       
  expo               51.0.39      managed                                             

Ignite
  ignite-cli         10.0.5       /Users/jbarkate/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/jbarkate/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               -            not installed 
  android home       -            undefined     

iOS
  xcode              16.1       
  cocoapods          1.16.2       /usr/local/bin/pod 

Tools
  git                git version 2.39.5 (Apple Git-154)   /usr/bin/git 

[JosephBarkate]

I removed the entire folder and re-installed using yarn it seems to work without this previous issue. Feel free to close this ticket if not useful.

[frankcalise]

@JosephBarkate thanks for the report, I couldn't reproduce this - could you supply your new command for me?

EDIT: nevermind you took the defaults, let me try again

[frankcalise]

Hmm yeah couldn't reproduce on node 20, wonder if it's specific to 21 and some npm upgrade (although I'm on 10.2.3)

[Allavaz]

just created a project using the defaults and got this error. it's weird because on first install it works fine, but if you try to install something else you get the error. i'm on node v20.12.2

[beefy24]

I removed the entire folder and re-installed using yarn it seems to work without this previous issue. Feel free to close this ticket if not useful.

@JosephBarkate What do you mean by removing the entire folder, the whole project?

I have the same issue. I can't install packages to the project with npm install.

Node 22.12.0
npm 10.9.0

[JosephBarkate]

@beefy24 , yea I removed the entire project to get a fresh repo. But it seems the issue is the package manager you choose. I had the error with npm but when I switched to yarn it worked. In there docs it seems they officially support yarn so there may be no support for npm.