You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Always follow the [upgrade guide](https://github.com/angular/angular-cli#updating-angular-cli) when upgrading to a new version. The changelog does not list breaking changes that are fixed via the update procedure.
2
+
3
+
<aname="1.0.0-beta.6"></a>
4
+
# 1.0.0-beta.6 (2016-06-13)
5
+
6
+
### Features
7
+
- Admin elevation no longer required on Windows (https://github.com/angular/angular-cli/pull/905).
8
+
- Automatically add SASS/Stylus if project is initialized with `--style={sass|scss|styl}` (https://github.com/angular/angular-cli/pull/998).
9
+
- Allow any number of env files (https://github.com/angular/angular-cli/pull/913).
10
+
11
+
### Bug Fixes
12
+
- Fix adding 3rd party libs without package format (https://github.com/angular/angular-cli/pull/1028/commits/065e98f40384f8b28dcaf84028c411043697ff11).
13
+
- Fix github deploy deep links (https://github.com/angular/angular-cli/pull/1020).
- Fix github user pages base href (https://github.com/angular/angular-cli/pull/965).
17
+
18
+
### BREAKING CHANGES
19
+
-`<PROJECT-NAME>AppComponent` is now simply `AppComponent`, and it's selector is now `app-root` (https://github.com/angular/angular-cli/pull/1042).
20
+
21
+
- Route generation is temporarily disabled while we move to the [recently announce router](http://angularjs.blogspot.ie/2016/06/improvements-coming-for-routing-in.html)(https://github.com/angular/angular-cli/pull/992). It is recommended that users manually move to this router in all new projects.
22
+
23
+
<aname="1.0.0-beta.5"></a>
24
+
# 1.0.0-beta.5 (2016-05-19)
25
+
26
+
### Known Issues
27
+
28
+
-`ng new -mobile` fails npm install (https://github.com/angular/angular-cli/issues/958).
29
+
- Adding 3rd party libs without SystemJS package format breaks prod mode (https://github.com/angular/angular-cli/issues/951).
30
+
- Deep links do not work on Github pages deploys (https://github.com/angular/angular-cli/issues/995).
31
+
-`ng e2e` doesn't return error exit code on test failures (https://github.com/angular/angular-cli/issues/1017).
32
+
-`ng build -prod` fails on mobile projects due to missing vendor file (https://github.com/angular/angular-cli/issues/847).
33
+
- Github deploy to user pages doesn't use correct base href (https://github.com/angular/angular-cli/pull/965).
34
+
-`ng test` on windows hits the file discriptor limit (https://github.com/angular/angular-cli/issues/977).
35
+
-`ng serve/build/test` need admin elevation on Windows (https://github.com/angular/angular-cli/issues/641).
*[3rd Party Library Installation](#3rd-party-library-installation)
40
+
*[Updating angular-cli](#updating-angular-cli)
39
41
*[Known Issues](#known-issues)
42
+
*[Development Hints for hacking on angular-cli](#development-hints-for-hacking-on-angular-cli)
40
43
41
44
## Installation
42
45
@@ -66,7 +69,7 @@ You can configure the default HTTP port and the one used by the LiveReload serve
66
69
ng serve --port 4201 --live-reload-port 49153
67
70
```
68
71
69
-
### Generating other scaffolds
72
+
### Generating Components, Directives, Pipes and Services
70
73
71
74
You can use the `ng generate` (or just `ng g`) command to generate Angular components:
72
75
@@ -90,6 +93,9 @@ Component | `ng g component my-new-component`
90
93
Directive | `ng g directive my-new-directive`
91
94
Pipe | `ng g pipe my-new-pipe`
92
95
Service | `ng g service my-new-service`
96
+
Class | `ng g class my-new-class`
97
+
Interface | `ng g interface my-new-interface`
98
+
Enum | `ng g enum my-new-enum`
93
99
94
100
### Generating a route
95
101
@@ -102,7 +108,7 @@ ng generate route hero
102
108
103
109
This will create a folder which will contain the hero component and related test and style files.
104
110
105
-
The generated route will also be registered with the parent component's `@RouteConfig` decorator.
111
+
The generated route will also be registered with the parent component's `@RouteConfig` decorator.
106
112
107
113
By default the route will be designated as a **lazy** route which means that it will be loaded into the browser when needed, not upfront as part of a bundle.
108
114
@@ -130,16 +136,22 @@ current cli environment.
130
136
Environment defaults to `dev`, but you can generate a production build via
131
137
the `-prod` flag in either `ng build -prod` or `ng serve -prod`.
132
138
139
+
You can also add your own env files other than `dev` and `prod` by creating a
140
+
`src/client/app/environment.{NAME}.ts` and use them by using the `--env=NAME`
141
+
flag on the build/serve commands.
142
+
133
143
### Running unit tests
134
144
135
145
```bash
136
146
ng test
137
147
```
138
148
139
-
Tests will execute after a build is executed via [Karma](http://karma-runner.github.io/0.13/index.html)
149
+
Tests will execute after a build is executed via [Karma](http://karma-runner.github.io/0.13/index.html), and it will automatically watch your files for changes.
150
+
151
+
You can run tests a single time via `--watch=false`, and turn off building of the app via `--build=false` (useful for running it at the same time as `ng serve`).
140
152
141
-
If run with the watch argument `--watch` (shorthand `-w`) builds will run when source files have changed
142
-
and tests will run after each successful build
153
+
**WARNING:** On Windows, `ng test` is hitting a file descriptor limit (see https://github.com/angular/angular-cli/issues/977).
154
+
The solution for now is to instead run `ng serve` and `ng test --build=false` in separate console windows.
143
155
144
156
145
157
### Running end-to-end tests
@@ -235,13 +247,39 @@ The `Angular2App`'s options argument has `sassCompiler`, `lessCompiler`, `stylus
235
247
236
248
The installation of 3rd party libraries are well described at our [Wiki Page](https://github.com/angular/angular-cli/wiki/3rd-party-libs)
237
249
250
+
### Updating angular-cli
251
+
252
+
To update `angular-cli` to a new version, you must update both the global package and your project's local package.
253
+
254
+
Global package:
255
+
```
256
+
npm uninstall -g angular-cli
257
+
npm cache clean
258
+
npm install -g angular-cli@latest
259
+
```
260
+
261
+
Local project package:
262
+
```
263
+
rm -rf node_modules dist tmp
264
+
npm install --save-dev angular-cli@latest
265
+
ng init
266
+
```
267
+
268
+
Running `ng init` will check for changes in all the auto-generated files created by `ng new` and allow you to update yours. You are offered four choices for each changed file: `y` (overwrite), `n` (don't overwrite), `d` (show diff between your file and the updated file) and `h` (help).
269
+
270
+
Carefully read the diffs for each code file, and either accept the changes or incorporate them manually after `ng init` finishes.
271
+
272
+
**The main cause of errors after an update is failing to incorporate these updates into your code**.
273
+
274
+
You can find more details about changes between versions in [CHANGELOG.md](https://github.com/angular/angular-cli/blob/master/CHANGELOG.md).
275
+
276
+
238
277
## Known issues
239
278
240
279
This project is currently a prototype so there are many known issues. Just to mention a few:
241
280
242
281
- All blueprints/scaffolds are in TypeScript only, in the future blueprints in all dialects officially supported by Angular will be available.
243
282
- On Windows you need to run the `build` and `serve` commands with Admin permissions, otherwise the performance is not good.
244
-
-[Protractor](https://angular.github.io/protractor/) integration is missing.
245
283
- The initial installation as well as `ng new` take too long because of lots of npm dependencies.
246
284
- Many existing ember addons are not compatible with Angular apps built via angular-cli.
247
285
- When you `ng serve` remember that the generated project has dependencies that require **Node 4 or greater**.
@@ -268,7 +306,7 @@ Now you can use `angular-cli` via the command line:
268
306
ng new foo
269
307
cd foo
270
308
npm link angular-cli
271
-
ng server
309
+
ng serve
272
310
```
273
311
274
312
`npm link angular-cli` is needed because by default the globally installed `angular-cli` just loads
This project was generated with [angular-cli](https://github.com/angular/angular-cli) version <%= version %>.
4
+
5
+
## Development server
6
+
Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
7
+
8
+
## Code scaffolding
9
+
10
+
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive/pipe/service/route/class`.
11
+
12
+
## Build
13
+
14
+
Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.
15
+
16
+
## Running unit tests
17
+
18
+
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
19
+
20
+
## Running end-to-end tests
21
+
22
+
Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
23
+
Before running the tests make sure you are serving the app via `ng serve`.
24
+
25
+
## Deploying to Github Pages
26
+
27
+
Run `ng github-pages:deploy` to deploy to Github Pages.
28
+
29
+
## Further help
30
+
31
+
To get more help on the `angular-cli` use `ng --help` or go check out the [Angular-CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
0 commit comments