We've been a Windows shop, mainly relying on Visual Studio as our IDE and build tool. We've begun to explore using Angular and node, and angular-cli.
We have a project that depends upon "angular-cli": "1.0.0-beta.10". I was trying to get this to build on a new machine.
I installed nodejs, then did a global install of angular-cli using npm:
npm install -g angular-cli
It seems like you're using a project generated using an old version of the Angular CLI.
The latest CLI now uses webpack and has a lot of improvements including a simpler
workflow, a faster build, and smaller bundles.
To get more info, including a step-by-step guide to upgrade the CLI, follow this link:
npm uninstall -g angular-cli
npm install -g email@example.com
The Angular-CLI can be run with, and the global
ng command uses, a locally installed version for each project. This local version can be accessed using the command
I recommend uninstalling the global CLI you have and taking the time to modify your package.json
scripts to reference the local CLI installation rather than the global
ng. This is my method to handle varied CLIs on my Jenkins server.
On that note, I do highly suggest following the instructions to move from Beta.10 to Beta.14 (https://github.com/angular/angular-cli/wiki/Upgrading-from-Beta.10-to-Beta.14) if you can stomach the change to WebPack. Any projects utilizing CLI Beta.14 or higher can be upgraded to Beta.21 simply by uninstalling the CLI, reinstalling it, and then running
ng init (
Diff [d] any files you've modified!) to update the boilerplate.