Customizable admin dashboard template based on Angular 10+

  • By Akveo
  • Last update: Dec 31, 2022
  • Comments: 16

ngx-admin Eva Design System Build Status

Who uses ngx-admin?| Documentation | Installation Guidelines | Angular templates

New! Material theme for ngx-admin

Material admin theme is based on the most popular Angular dashboard template - ngx-admin To use material theme checkout feat/material-theme branch.

Get material ngx-admin integrated with backend technology of your choice. Check out our store.

Key features

  • The most popular and trusted Angular open source dashboard template is out there. Used by hundreds of thousands developers worldwide and Fortune 500 companies*.
  • Over 40+ Angular Components and 60+ Usage Examples. Kick off your project and save money by using ngx-admin.
  • Already using ngx-admin and willing to switch to material theme? Material theme is backward-compatible. Check out the article describing how to do that.
  • ngx-admin material works perfectly with Angular Material and Nebular. Take the best from both!

To use material theme checkout feat/material-theme branch

Admin template based on Angular 10+ and Nebular

UI Bakery

Try low-code internal tool builder for free

Check out our Store for ready to use Backend Bundles.

Free Bundles

With 6 stunning visual themes
Material Dark Material Light
Dark Default
Cosmic Corporate

What's included:

  • Angular 10+ & Typescript
  • Bootstrap 4+ & SCSS
  • Responsive layout
  • RTL support
  • High resolution
  • Flexibly configurable themes with hot-reload (3 themes included)
  • Authentication module with multiple providers
  • 40+ Angular Components
  • 60+ Usage Examples

Demo

Live Demo

Documentation

This template is using Nebular modules set, here you can find documentation and other useful articles.

Empty starter kit

Don't need all the pages and modules and just looking for an empty starter kit for your next project? Check out our starter-kit branch.

BrowserStack

This project runs its tests on multiple desktop and mobile browsers using BrowserStack.

More from Akveo

  • Eva Icons - 480+ beautiful Open Source icons
  • Nebular - Angular Components, Auth and Security
  • Akveo templates - 10+ Ready-to-use apps templates to speed up your apps developments

How can I support developers?

  • Star our GitHub repo ⭐
  • Create pull requests, submit bugs, suggest new features or documentation updates 🔧
  • Follow us on Twitter 🐾
  • Like our page on Facebook 👍

Looking for engineering services?

Visit our homepage or simply leave us a message to [email protected]. We will be happy to work with you!

From Developers

Made with ❤️ by Akveo team. Follow us on Twitter to get the latest news first! We're always happy to receive your feedback!

Github

https://github.com/akveo/ngx-admin

Comments(16)

  • 1

    Do you plan move project to angular-cli ?

    • I'm submitting a ... [ ] bug report [ ] feature request [*] question about the decisions made in the repository

    Do you plan move your project to angular-cli ?

  • 2

    Add JWT automatically for every HTTP request

    Is it possible to add a JWT to the HTTP header for every request? How can I achieve this? I need every request to be authenticated with an authorization token by my backend.

    Any help is appreciated!

  • 3

    Stuck on Build Production

    • I'm submitting a ... [x] bug report [ ] feature request [ ] question about the decisions made in the repository

    • Do you want to request a feature or report a bug?

    • What is the current behavior? When i try to build for production its just stuck and not compliitng.

    it stuck on this line

    61% building modules 593/692 modules 99 active ...n-orignal/src/app/pages/pages.menu.ts

  • 4

    Breaking changes: can not create custom login page

    See my second comment for the working workaround.

    I suspect that everyone that has a custom login page is affected.

    Issue type

    I'm submitting a ... (check one with "x")

    • [X] bug report
    • [ ] feature request
    • [ ] question about the decisions made in the repository

    Issue description

    Current behavior: When i try to implement a custom login page as described in https://akveo.github.io/nebular/docs/auth/configuring-ui#custom-ui-components i get some errors.

    1. 'nb-alert' is not a known element. My solution is to change theme.module.ts in ngx-admin to: import { NbAlertModule, //I added this line NbActionsModule, NbCardModule, NbLayoutModule, NbMenuModule, NbRouteTabsetModule, NbSearchModule, NbSidebarModule, NbTabsetModule, NbThemeModule, NbUserModule, NbCheckboxModule, NbPopoverModule, NbContextMenuModule, } from '@nebular/theme';

    And: const NB_MODULES = [ NbAlertModule, //I added this line NbCardModule, NbLayoutModule, NbTabsetModule, NbRouteTabsetModule, NbMenuModule, NbUserModule, NbActionsModule, NbSearchModule, NbSidebarModule, NbCheckboxModule, NbPopoverModule, NbContextMenuModule, NgbModule, NbSecurityModule, // *nbIsGranted directive ];

    1. After that i get this error: Error: Template parse errors: Can't bind to 'status' since it isn't a known property of 'input'. (" autofocus fullWidth [ERROR ->][status]="email.dirty ? (email.invalid ? 'danger' : 'success') : ''" [required]="ge"): ng:///ThemeModule/[email protected]:17 Can't bind to 'status' since it isn't a known property of 'input'. (" placeholder="Password" fullWidth [ERROR ->][status]="password.dirty ? (password.invalid ? 'danger' : 'success') : ''" [require"): ng:///ThemeModule/[email protected]:17 Can't bind to 'routerLink' since it isn't a known property of 'a'. ("r *ngFor="let socialLink of socialLinks"> <a *ngIf="socialLink.link" [ERROR ->][routerLink]="socialLink.link" [attr.target]="socialLink.target" [a"): ng:///ThemeModule/[email protected]:17 'nb-auth-block' is not a known element:
    2. If 'nb-auth-block' is an Angular component, then verify that it is part of this module.
    3. If 'nb-auth-block' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message. (" [ERROR ->] Hello! "): ng:///ThemeModule/[email protected]:4

    I am trying to find a solution for this as we speak. It looks like in my custom login component

    input nbInput the directive is not recognized, so i have to find a way to import it in my themes.module.ts, but the input directive in @nebular/components is missing.

    Steps to reproduce: Install from scratch and try to create a custom login page

    Related code: This problem is related to Feat/auth button input # 595 in the nebular repository.

  • 5

    HTML 5 Routing

    Sort of a bug, but more of a feature request.

    What is the effort to convert links to HTML 5 routes versus hash routing? Angular recommends using HTML 5 routing over hash routing. Has routing also does not appear to work with auth0 although I am seeking support from them for help.

    When I set hash routing to false in app.routing.ts:

    export const routing = RouterModule.forRoot(routes, { useHash: false });

    The initial page will load, but all links will be broken.

  • 6

    Feature, Menu disable, hidden

    • I'm submitting a ... [ ] bug report [x] feature request [ ] question about the decisions made in the repository

    • Do you want to request a feature ?

    To make it easier working with the project as starter it would be nice if we have 2 new options in pages.menu.

    hidden: true, false

    • Sets the menu point invisible. This makes it easier if we update the project with new versions, so we only have to set the menu points hidden again and don´t have to delete them from the file.

    disable: true

    • Menu points should be written in grey. This would make it possible to show user permisions already in the menu. E.g user X is not allowed to acces dashboard so its written in grey and he can´t click on it.

    I build this ugly by my own, but I´m sure more people would have a use of it.

    • What is the current behavior?

    Pages.menu and pages.routing contain the Pages. To remove one you have to change both files.

  • 7

    Error: HtmlWebpackPlugin: could not load file vendor.dll.js.map

    • I'm submitting a ... [x ] bug report [ ] feature request [ ] question about the decisions made in the repository

    • Do you want to request a feature or report a bug? Report a bug

    • What is the current behavior? It compiles, but doesnt really work...

    • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

    • What is the expected behavior? The expected behaviour is that it should work

    • What is the motivation / use case for changing the behavior?

    • Please tell us about your environment: Latest commit @ Windows, Node 7.5.0

    • Angular version: 2.0.0-rc.X
    • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

    `Html Webpack Plugin: Error: HtmlWebpackPlugin: could not load file C:\Users\PerArneA\IdeaProjects\s ondre-prosjekt\dll\vendor.dll.js.map

    • index.js:313 [sondre-prosjekt]/[html-webpack-plugin]/index.js:313:27

    • util.js:16 tryCatcher [sondre-prosjekt]/[bluebird]/js/release/util.js:16:23

    • promise.js:510 Promise._settlePromiseFromHandler [sondre-prosjekt]/[bluebird]/js/release/promise.js:510:31

    • promise.js:567 Promise._settlePromise [sondre-prosjekt]/[bluebird]/js/release/promise.js:567:18

    • promise.js:612 Promise._settlePromise0 [sondre-prosjekt]/[bluebird]/js/release/promise.js:612:10

    • promise.js:687 Promise._settlePromises [sondre-prosjekt]/[bluebird]/js/release/promise.js:687:18

    • async.js:133 Async._drainQueue [sondre-prosjekt]/[bluebird]/js/release/async.js:133:16

    • async.js:143 Async._drainQueues [sondre-prosjekt]/[bluebird]/js/release/async.js:143:10

    • async.js:17 Immediate.Async.drainQueues [sondre-prosjekt]/[bluebird]/js/release/async.js:17:14 `

  • 8

    npm start throw Data path ".builders['app-shell']" should have required property 'class'

    Issue description

    Current behavior: Not able to start the project.

    Expected behavior: Project started

    Steps to reproduce: npm start

    Other information:

    npm, node, OS, Browser

    Schema validation failed with the following errors:
  Data path ".builders['app-shell']" should have required property 'class'.
Error: Schema validation failed with the following errors:
  Data path ".builders['app-shell']" should have required property 'class'.

    Node, npm: `v10.15.0` and `6.9.0`
OS: macOS (Mojave)
  • 9

    Integrate with ASP.NET MVC 5

    • I'm submitting a ... [ ] bug report [ X ] feature request [ ] question about the decisions made in the repository

    • Do you want to request a feature or report a bug?

    Integrate with ASP.NET MVC 5 is possible, steps, tutorial???

  • 10

    Update Angular Packages 2.0.0-rc.5

    • I'm submitting a ... [ ] bug report [x ] feature request [ ] question about the decisions made in the repository
    • Do you want to request a feature or report a bug? Update the angular packages to the latest 2.0.0-rc.5, the main reason for that is to be able to use @NgModule decorator

    Tried myself but no success, once I run npm start webpack doesn't compile.

    Thanks

  • 11

    Fail to start application

    • I'm submitting a ... [X] bug report [ ] feature request [ ] question about the decisions made in the repository
    • Do you want to request a feature or report a bug? I want report a bug
    • What is the current behavior? The app don't start. The terminal error is: "ng2-admin/node_modules/ng2-ckeditor/CKEditor.d.ts:7:36 Cannot find module '@angular/forms'."
    • Steps
    • git clone
    • npm install
    • npm start
    • access localhost:3000
    • Please tell us about your environment:
    • Angular version: 2.0.0-rc.3 (defined in package.json)
    • Browser: all
  • 12

    Dockerization with Ngnix

    Please read and mark the following check list before creating a pull request (check one with "x"):

    Short description of what this resolves:

  • 13

    release: 9.0.0

    Please read and mark the following check list before creating a pull request (check one with "x"):

    Short description of what this resolves:

  • 14

    error in npm install ngx-admin 7.0.0

    Issue type

    I'm submitting a ... (check one with "x")

    • [x] bug report
    • [ ] feature request
    • [ ] question about the decisions made in the repository

    Issue description

    I'm having dependencies error in npm install. I deleted package.lock.json and node_modules before doing npm install Current behavior:

    image

    Expected behavior:

    Npm install will run without error

    Steps to reproduce:

    Npm install Related code:

    Other information:

    image

    image

  • 15

    Installation does not work when following the documentation

    Issue type

    I'm submitting a ... (check one with "x")

    • [x] bug report
    • [ ] feature request
    • [ ] question about the decisions made in the repository

    Issue description

    Installation does not work when steps from the documentation are followed. What could be the reason?

    Windows 10, npm 8.1.2, node 16.13.2

    Below the log:

     npm i --force
npm WARN using --force Recommended protections disabled.
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/typescript
npm WARN   dev [email protected]"~4.2.3||~4.3.0" from the root project
npm WARN   3 more (@compodoc/ngd-core, tsutils, tslint)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer [email protected]">= 2.3.1 < 3" from [email protected]
npm WARN node_modules/tslint-language-service
npm WARN   dev [email protected]"^0.9.9" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @angular/[email protected]
npm WARN node_modules/@angular/common
npm WARN   @angular/[email protected]"^12.2.16" from the root project
npm WARN   14 more (@akveo/ng2-completer, @angular/cdk, @angular/forms, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN node_modules/ng2-ckeditor
npm WARN   [email protected]"~1.2.9" from the root project
npm WARN
npm WARN Conflicting peer dependency: @angular/[email protected]
npm WARN node_modules/@angular/common
npm WARN   peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN   node_modules/ng2-ckeditor
npm WARN     [email protected]"~1.2.9" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @angular/[email protected]
npm WARN node_modules/@angular/core
npm WARN   @angular/[email protected]"^12.2.16" from the root project
npm WARN   16 more (@akveo/ng2-completer, @angular/cdk, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN node_modules/ng2-ckeditor
npm WARN   [email protected]"~1.2.9" from the root project
npm WARN
npm WARN Conflicting peer dependency: @angular/[email protected]
npm WARN node_modules/@angular/core
npm WARN   peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN   node_modules/ng2-ckeditor
npm WARN     [email protected]"~1.2.9" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @angular/[email protected]
npm WARN node_modules/@angular/forms
npm WARN   @angular/[email protected]"^12.2.16" from the root project
npm WARN   3 more (@akveo/ng2-completer, @nebular/auth, ng2-completer)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN node_modules/ng2-ckeditor
npm WARN   [email protected]"~1.2.9" from the root project
npm WARN
npm WARN Conflicting peer dependency: @angular/[email protected]
npm WARN node_modules/@angular/forms
npm WARN   peer @angular/[email protected]"^10.0.4" from [email protected]
npm WARN   node_modules/ng2-ckeditor
npm WARN     [email protected]"~1.2.9" from the root project
npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated [email protected]: The package has been renamed to `open`
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @types/[email protected]: Types for the Google Maps browser API have moved to @types/google.maps. Note: these types are not for the googlemaps npm package, which is a Node API.
npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated [email protected]: We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular
npm WARN deprecated [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated [email protected]: [email protected]<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: [email protected]<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: We have renamed the @ckeditor package. New versions are available under the @ckeditor4 name.
npm ERR! code 1
npm ERR! path C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js
npm ERR! Building: C:\Program Files\nodejs\node.exe C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
npm ERR! Build started 31/08/2022 18:11:38.
npm ERR! Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.sln" on node 1 (default targets).
npm ERR! ValidateSolutionConfiguration:
npm ERR!   Building solution configuration "Release|x64".
npm ERR! Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.sln" (1) is building "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.vcxproj.metaproj" (2) on node 1 (default targets).
npm ERR! Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.vcxproj.metaproj" (2) is building "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\src\libsass.vcxproj" (3) on node 1 (default targets).
npm ERR! C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\src\libsass.vcxproj(21,3): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
npm ERR! Done Building Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\src\libsass.vcxproj" (default targets) -- FAILED.
npm ERR! Done Building Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.vcxproj.metaproj" (default targets) -- FAILED.
npm ERR! Done Building Project "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.sln" (default targets) -- FAILED.
npm ERR!
npm ERR! Build FAILED.
npm ERR!
npm ERR! "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.sln" (default target) (1) ->
npm ERR! "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\binding.vcxproj.metaproj" (default target) (2) ->
npm ERR! "C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\src\libsass.vcxproj" (default target) (3) ->
npm ERR!   C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\src\libsass.vcxproj(21,3): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
npm ERR!
npm ERR!     0 Warning(s)
npm ERR!     1 Error(s)
npm ERR!
npm ERR! Time Elapsed 00:00:00.19
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli   'C:\\Program Files\\nodejs\\node.exe',
npm ERR! gyp verb cli   'C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-gyp\\bin\\node-gyp.js',
npm ERR! gyp verb cli   'rebuild',
npm ERR! gyp verb cli   '--verbose',
npm ERR! gyp verb cli   '--libsass_ext=',
npm ERR! gyp verb cli   '--libsass_cflags=',
npm ERR! gyp verb cli   '--libsass_ldflags=',
npm ERR! gyp verb cli   '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "C:Python27python.exe" in the PATH
npm ERR! gyp verb `which` failed Error: not found: C:Python27python.exe
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21)
npm ERR! gyp verb `which` failed  C:Python27python.exe Error: not found: C:Python27python.exe
npm ERR! gyp verb `which` failed     at getNotFoundError (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21) {
npm ERR! gyp verb `which` failed   code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb could not find "C:Python27python.exe". checking python launcher
npm ERR! gyp verb check python launcher python executable found: "C:\\Python27\\python.exe"
npm ERR! gyp verb check python version `C:\Python27\python.exe -c "import sys; print "2.7.10
npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 16.13.2
npm ERR! gyp verb command install [ '16.13.2' ]
npm ERR! gyp verb install input version string "16.13.2"
npm ERR! gyp verb install installing version: 16.13.2
npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed
npm ERR! gyp verb install version is already installed, need to check "installVersion"
npm ERR! gyp verb got "installVersion" 9
npm ERR! gyp verb needs "installVersion" 9
npm ERR! gyp verb install version is good
npm ERR! gyp verb get node dir target node version installed: 16.13.2
npm ERR! gyp verb build dir attempting to create "build" dir: C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build
npm ERR! gyp verb build dir "build" dir needed to be created? C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build
npm ERR! gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
npm ERR! gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.Windows10SDK.19041
npm ERR! gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64
npm ERR! gyp verb find vs2017   - Found Microsoft.VisualStudio.VC.MSBuild.Base
npm ERR! gyp verb find vs2017   - Using this installation with Windows 10 SDK
npm ERR! gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
npm ERR! gyp verb build/config.gypi creating config file
npm ERR! gyp verb build/config.gypi writing out config file: C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\build\config.gypi
npm ERR! (node:9040) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp verb config.gypi checking for gypi file: C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\config.gypi
npm ERR! gyp verb common.gypi checking for gypi file: C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass\common.gypi
npm ERR! gyp verb gyp gyp format was not specified; forcing "msvs"
npm ERR! gyp info spawn C:\Python27\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'msvs',
npm ERR! gyp info spawn args   '-G',
npm ERR! gyp info spawn args   'msvs_version=2015',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-sass\\build\\config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\rafal\\.node-gyp\\16.13.2\\include\\node\\common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=C:\\Users\\rafal\\.node-gyp\\16.13.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=C:\\Users\\rafal\\.node-gyp\\16.13.2\\<(target_arch)\\node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-sass',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-sass\\build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp verb command build []
npm ERR! gyp verb build type Release
npm ERR! gyp verb architecture x64
npm ERR! gyp verb node dev dir C:\Users\rafal\.node-gyp\16.13.2
npm ERR! gyp verb found first Solution file build/binding.sln
npm ERR! gyp verb `which` succeeded for `msbuild` C:\Windows\Microsoft.NET\Framework64\v4.0.30319\msbuild.EXE
npm ERR! gyp info spawn msbuild
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'build/binding.sln',
npm ERR! gyp info spawn args   '/nologo',
npm ERR! gyp info spawn args   '/p:Configuration=Release;Platform=x64'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `msbuild` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onExit (C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-gyp\lib\build.js:262:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Windows_NT 10.0.19044
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\rafal\\Documents\\admin-experiment\\ngx-admin\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd C:\Users\rafal\Documents\admin-experiment\ngx-admin\node_modules\node-sass
npm ERR! gyp ERR! node -v v16.13.2
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1
  • 16

    Dependency issues on installation

    Issue type

    I'm submitting a ...

    • [X] bug report

    Issue description

    Current behavior: When running npm install I get the following:

    npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/[email protected]"^12.2.16" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/[email protected]"~9.1.1" from @swimlane/[email protected]
npm ERR! node_modules/@swimlane/ngx-charts
npm ERR!   @swimlane/[email protected]"^14.0.0" 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.

    Expected behavior: Everything would just install.

    Steps to reproduce: Clone the repo, run npm install

    Other information:

    npm, node, OS, Browser

    Angular CLI: 12.2.12
Node: 18.3.0 (Unsupported)
Package Manager: npm 8.11.0
OS: Mac Monterey 12.4 (Intel)

    Angular, Nebular

        "@nebular/auth": "8.0.0",
    "@nebular/eva-icons": "8.0.0",
    "@nebular/security": "8.0.0",
    "@nebular/theme": "8.0.0",
    "nebular-icons": "1.1.0",

Popular Tag

Related