angular-docs-cn/integration/ivy-i18n
George Kalpakas 4ece0eb27c build: use exact versions for integration project dependencies (#33968)
Since we cannot run `yarn install` with the `--frozen-lockfile` option
(because we want to be able to install the locally built Angular
packages), integration project lockfiles are susceptible to getting
out-of-sync with the corresponding `package.json`. When this happens,
yarn will install the latest available version that satisfies the
version range specified in `package.json`.

This commit adds another line of defense, by specifying exact versions
for the dependencies in `package.json` files (i.e. `1.33.7` instead of
`^1.33.0`). While transitive dependencies will be unpinned, this still
ensures that the same version of direct dependencies will be installed
in case of an out-of-sync lockfile, thus reducing the probability of
random failures.

PR Close #33968
2019-11-26 16:08:32 -08:00
..
e2e test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
src fix(ivy): i18n - ensure that colons in i18n metadata are not rendered (#33820) 2019-11-18 16:00:22 -08:00
.editorconfig test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
.gitignore test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
README.md test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
angular.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
browserslist test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
debug-test.sh build: make ivy-i18n/debug-test.sh executable (#33820) 2019-11-18 16:00:22 -08:00
karma.conf.js test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
package.json build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00
tsconfig.app.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tsconfig.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tsconfig.legacy-xmb.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tsconfig.legacy.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tsconfig.spec.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tsconfig.view-engine.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
tslint.json test: rename cli-hello-world-ivy-i18n to just ivy-i18n (#33510) 2019-11-01 17:50:56 +00:00
yarn.lock build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00

README.md

CliHelloWorldIvyI18n

This project was generated with Angular CLI version 9.0.0-next.9.

Development server

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.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

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.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.