[ERROR] An error occurred while running subprocess npm

Ionic Framework
1

hi, i have a big problem with ionic. I cannot create a new project. when I type:
ionic start myApp tabs, I have this answer:
C:\Users\USER\Desktop\application>ionic start myApp tabs

Pick a framework!

Please select the JavaScript framework to use for your new app. To bypass this prompt next time, supply a value for the
–type option.

? Framework: Angular
? .\myApp exists. Overwrite? Yes
√ Preparing directory .\myApp - done!
√ Downloading and extracting tabs starter - done!

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

    Learn more: https://ion.link/appflow

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

npm.cmd i
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Unexpected end of JSON input while parsing near ‘…9f6N3c/9VT8p7bmtZoJst’

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USER\AppData\Roaming\npm-cache_logs\2020-01-30T19_06_55_632Z-debug.log
[ERROR] An error occurred while running subprocess npm.

    npm.cmd i exited with exit code 1.

    Re-running this command with the --verbose flag may provide more information.
2

Did you find any solution I’m having same issue too.

3

non hoo personne ne veux me répondre

4

Getting same issue , did anyone solved?

Edit 1: Update node will resolve this issue

5

Hi please have you solved this problem? I am having same problem

6

@SalimSulaiman did your error is similar to this :thinking:

7

Hi. Have you solved this problem? I am facing same problem

8

not right now, but I created a react project then initializing it with ionic init worked(get to worked) for me

9

Have you found a solution?

10

switched to Ubuntu :sweat_smile:

11

Ok. Mine is working now

12

works for me:
npm cache clean --force

13

how did u solve this

14

Downgrade your node version, that is what I did and it worked for me. Preferably downgrade to the stable version