Prototype of a CLI for Angular 2 applications based on the ember-cli project.
This projects is very much still a work in progress.
We still have a long way before getting out of our alpha stage. If you wish to collaborate while the project is still young, checkout our list issues.
The generated project has dependencies that require Node 4 or greater.
npm install -g angular-cling --helpng new PROJECT_NAME
cd PROJECT_NAME
ng serveNavigate to [http://localhost:4200/]. The app will automatically reload if you change any of the source files.
Add a new component with:
ng generate component my-new-componentAdd a new service with:
ng generate service my-new-serviceAdd a new pipe with:
ng generate pipe my-new-pipeng buildThe build artifacts will be stored in the dist/ directory.
Before running the tests make sure that the project is built. To build the project once you can use:
ng buildWith the project built in the dist/ folder you can just run: karma start.
Karma will run the tests and keep the browser open waiting to run again.
This will be easier when the command ng test is implemented.
The CLI currently comes bundled with angular-cli-github-pages addon.
This means that you can deploy your apps quickly via:
git commit -a -m "final tweaks before deployment - what could go wrong?"
ng github-pages:deploy
Checkout angular-cli-github-pages addon docs for more info.
This project is currently a prototype so there are many known issues. Just to mention a few:
- All blueprints/scaffolds are in TypeScript only, in the future blueprints in all dialects officially supported by Angular will be available.
- On Windows you need to run the
buildandservecommands with Admin permissions otherwise the performance really sucks. - Protractor integration is missing.
- The initial installation as well as
ng newtake too long because of lots of npm dependencies. - "ember" branding leaks through many error messages and help text.
- Many existing ember addons are not compatible with Angular apps built via angular-cli.
git clone https://github.com/angular/angular-cli.git
cd angular-cli
npm linknpm link is very similar to npm install -g except that instead of downloading the package
from the repo, the just cloned angular-cli/ folder becomes the global package.
Any changes to the files in the angular-cli/ folder will immediately affect the global angular-cli package,
allowing you to quickly test any changes you make to the cli project.
Now you can use angular-cli via the command line:
ng new foo
cd foo
npm link angular-cli
ng servernpm link angular-cli is needed because by default the globally installed angular-cli just loads
the local angular-cli from the project which was fetched remotely from npm.
npm link angular-cli symlinks the global angular-cli package to the local angular-cli package.
Now the angular-cli you cloned before is in three places:
The folder you cloned it into, npm's folder where it stores global packages and the angular-cli project you just created.
Please read the official npm-link documentation and the npm-link cheatsheet for more information.
Apache v2