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
Copy file name to clipboardExpand all lines: README.md
+17-16
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,13 @@ Prototype of a CLI for Angular 2 applications based on the [ember-cli](http://ww
13
13
14
14
This project is very much still a work in progress.
15
15
16
-
The CLI is now in beta.
16
+
The CLI is now in beta.
17
17
If you wish to collaborate while the project is still young, check out [our issue list](https://github.com/angular/angular-cli/issues).
18
18
19
19
## Webpack update
20
20
21
-
We changed the build system between beta.10 and beta.14, from SystemJS to Webpack.
22
-
And with it comes a lot of benefits.
21
+
We changed the build system between beta.10 and beta.14, from SystemJS to Webpack.
22
+
And with it comes a lot of benefits.
23
23
To take advantage of these, your app built with the old beta will need to migrate.
24
24
25
25
You can update your `beta.10` projects to `beta.14` by following [these instructions](https://github.com/angular/angular-cli/wiki/Upgrading-from-Beta.10-to-Beta.14).
@@ -109,6 +109,7 @@ Service | `ng g service my-new-service`
109
109
Class | `ng g class my-new-class`
110
110
Interface | `ng g interface my-new-interface`
111
111
Enum | `ng g enum my-new-enum`
112
+
Module | `ng g module my-module`
112
113
113
114
### Generating a route
114
115
@@ -126,8 +127,8 @@ The build artifacts will be stored in the `dist/` directory.
126
127
127
128
### Build Targets and Environment Files
128
129
129
-
`ng build` can specify both a build target (`--target=production` or `--target=development`) and an
130
-
environment file to be used with that build (`--environment=dev` or `--environment=prod`).
130
+
`ng build` can specify both a build target (`--target=production` or `--target=development`) and an
131
+
environment file to be used with that build (`--environment=dev` or `--environment=prod`).
131
132
By default, the development build target and environment are used.
132
133
133
134
The mapping used to determine which environment file is used can be found in `angular-cli.json`:
@@ -157,7 +158,7 @@ ng build
157
158
158
159
You can also add your own env files other than `dev` and `prod` by doing the following:
159
160
- create a `src/environments/environment.NAME.ts`
160
-
- add `{ "NAME": 'src/environments/environment.NAME.ts' }` to the the `apps[0].environments` object in `angular-cli.json`
161
+
- add `{ "NAME": 'src/environments/environment.NAME.ts' }` to the the `apps[0].environments` object in `angular-cli.json`
161
162
- use them via the `--env=NAME` flag on the build/serve commands.
162
163
163
164
### Base tag handling in index.html
@@ -172,7 +173,7 @@ ng build --bh /myUrl/
172
173
173
174
### Bundling
174
175
175
-
All builds make use of bundling, and using the `--prod` flag in `ng build --prod`
176
+
All builds make use of bundling, and using the `--prod` flag in `ng build --prod`
176
177
or `ng serve --prod` will also make use of uglifying and tree-shaking functionality.
177
178
178
179
### Running unit tests
@@ -290,11 +291,11 @@ source ~/.bash_profile
290
291
291
292
### Global styles
292
293
293
-
The `styles.css` file allows users to add global styles and supports
0 commit comments