# Ionic + Capacitor install error **URL:** \ **Category:** Ionic Framework\ **Created:** [March 13, 2021, 7:44am UTC](https://forum.ionicframework.com/t/ionic-capacitor-install-error/206448 "2021-03-13T07:44:05Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![\_va](https://avatars.discourse-cdn.com/v4/letter/_/b9e5f3/32.png) [@\_va](https://forum.ionicframework.com/u/_va)\ **Post date:** [March 13, 2021, 7:44am UTC](https://forum.ionicframework.com/t/ionic-capacitor-install-error/206448/1 "2021-03-13T07:44:05Z")
Hey @all, I try to create a new ionic project with capacitor, but got these error all the time: (I use ionic start for creation) ```auto npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/architect@0.1101.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/build-angular@0.1101.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/build-optimizer@0.1101.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/build-webpack@0.1101.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.2.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0 || ^7.5.6', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/schematics@11.2.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0 || ^7.5.6', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular/cli@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/schematics@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@ngtools/webpack@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@schematics/angular@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/schematics@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@schematics/update@0.1101.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/core@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@angular-devkit/schematics@11.1.4', npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0', yarn: '>= 1.13.0' }, npm WARN EBADENGINE current: { node: 'v14.14.0', npm: '7.5.3' } npm WARN EBADENGINE } up to date, audited 1759 packages in 2s 90 packages are looking for funding run `npm fund` for details 3 low severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force ``` current node: v14.14.0 current npm: 7.5.3 Any ideas how i can fix this issue and use capacitor? ---
**Author:** ![sebafra](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/sebafra/32/113464_2.png) [@sebafra](https://forum.ionicframework.com/u/sebafra)\ **Post date:** [March 22, 2021, 7:48pm UTC](https://forum.ionicframework.com/t/ionic-capacitor-install-error/206448/2 "2021-03-22T19:48:04Z")
Hi. There are warnings ---
**Author:** ![rapropos](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/rapropos/32/100227_2.png) [@rapropos](https://forum.ionicframework.com/u/rapropos)\ **Post date:** [March 22, 2021, 8:54pm UTC](https://forum.ionicframework.com/t/ionic-capacitor-install-error/206448/3 "2021-03-22T20:54:26Z")
The npm ecosystem is planetarily huge and constantly changing. In order to try to make _some_ sort of order out of the chaos, the notion of [semantic versioning](https://semver.org/) was born. Both library/package authors and consumers (people like you and me) make statements about what versions of things they consider to be acceptably compatible with their software. You have to make your own choices about what versions _you_ want to accept. Totally ignoring the wishes of the authors of your dependencies is certainly one strategy (see the above “don’t worry, they’re just warnings” comment), especially if you are interested in participating in the process of identifying and fixing compatibility problems. However, when you _do_ run into such a problem, the first thing anybody is going to tell you to do is to see if the problem persists when using approved versions of everything. If you would prefer not to deal with all that, then I would suggest _not_ ignoring the constraints that other authors have placed on their code. As is documented in [here](https://github.com/npm/node-semver#ranges), `^6.11.0` says “I can work with version `6.anything`, but not anything with a major version higher than 6”. I would recommend downgrading your npm to major version 6.