Ionic new app failed. No matching version found for @typescript-eslint/typescript-estree@6.18.0

Today (2023/01/12) I started a new project with Ionic.
Reading the documentation I understand that it is necessary to have Node v18 or higher.
I follow the steps of creating an app with ionic start, but an error occurs:

npm i --save -E @capacitor/core@latest exited with exit code 1.

With the --verbose arg I got this:

No matching version found for @typescript-eslint/typescript-estree@6.18.0

This happen several times with different node versions.

Details:

Ionic:

   Ionic CLI : 6.20.9

Utility:

   cordova-res : not installed globally
   native-run  : not installed globally

System:

   NodeJS : v20.11.0
   npm    : 10.2.4
   OS     : macOS Ventura

Full error:

? Project name: app

Let's pick the perfect starter template! πŸ’ͺ

Starter templates are ready-to-go Ionic apps that come packed with everything you need to build your app. To bypass this
prompt next time, supply template, the second argument to ionic start.

? Starter template: blank
βœ” Preparing directory ./app in 856.93ΞΌs
βœ” Downloading and extracting blank starter in 1.06s
> ionic integrations enable capacitor --quiet -- app io.ionic.starter
> npm i --save -E @capacitor/core@latest
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @typescript-eslint/typescript-estree@6.18.0.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: /Users/victorvalenzuela/.npm/_logs/2024-01-12T20_13_50_448Z-debug-0.log
[ERROR] An error occurred while running subprocess npm.
        
        npm i --save -E @capacitor/core@latest exited with exit code 1.
        
        Re-running this command with the --verbose flag may provide more information.

Installing dependencies may take several minutes.

  ──────────────────────────────────────────────────────────────

        Ionic Appflow, the mobile DevOps solution by Ionic

           Continuously build, deploy, and ship apps πŸš€
        Focus on building apps while we automate the rest 🎁

                 πŸ‘‰  https://ion.link/appflow  πŸ‘ˆ

  ──────────────────────────────────────────────────────────────


> npm i
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @typescript-eslint/typescript-estree@6.18.0.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: /Users/user/.npm/_logs/2024-01-12T20_14_00_743Z-debug-0.log
[ERROR] An error occurred while running subprocess npm.
        
        npm i exited with exit code 1.
        
        Re-running this command with the --verbose flag may provide more information.

How can I start a new project with last stable dependencies?

What’s your operating system?
Which options did you choose? (framework, template, etc.)

I just created an angular blank app from macOS without any problems

Hello, thanks for responde.

I will share more details:

MacOS Ventura

I tried with this Node versions:

   v16.20.0
   v16.20.2
   v18.16.0
   v18.19.0
   v20.11.0

As you know, the Ionic start command install the latest Capacitor version, so in that step fail.
Can you share with me more details about your setup?

In that step it installs all dependencies, not just Capacitor and the one failing to install is @typescript-eslint/typescript-estree, which is not a Capacitor dependency.

It’s probably a dependency from @typescript-eslint/eslint-plugin, which is one of the packages that all templates include, but they use different versions.

So, which framework did you choose? angular? react? vue?
which template? blank? tabs? other?

Hello,

I select tabs template with Angular, but I tried with blank and it failed as well.

@julio-ionic, please, can you share with me more details about your setup?

macOS Ventura
node v18.18.0
npm 9.8.1

Hello @julio-ionic, thanks for your time.
I tried something a bit desperate: starting the app on another laptop, running Windows, then copied the node_modules and ran this command:

chmod -R a+x node_modules

it works!