https://github.com/angular/angular
Revision f3eb7d9ecb9a82e7396cca658e3250e47c853153 authored by Andrew Scott on 27 April 2022, 18:53:30 UTC, committed by Dylan Hunn on 27 April 2022, 20:05:33 UTC
In order to survive closure minification correctly, static properties need to
be annotated with @nocollapse.

For more history, see https://github.com/angular/angular/pull/28050

PR Close #45783
1 parent b9a07d6
Raw File
Tip revision: f3eb7d9ecb9a82e7396cca658e3250e47c853153 authored by Andrew Scott on 27 April 2022, 18:53:30 UTC
fix(core): Ensure the `StandaloneService` is retained after closure minification (#45783)
Tip revision: f3eb7d9
yarn.lock.readme.md
All of our npm dependencies are locked via the `yarn.lock` file for the following reasons:

- our project has lots of dependencies which update at unpredictable times, so it's important that
  we update them explicitly once in a while rather than implicitly when any of us runs `yarn install`
- locked dependencies allow us to reuse yarn cache on CircleCI, significantly speeding up our builds
  (by 5 minutes or more)
- locked dependencies allow us to detect when node_modules folder is out of date after a branch switch
  which allows us to build the project with the correct dependencies every time

Before changing a dependency, do the following:

- make sure you are in sync with `upstream/master`: `git fetch upstream && git rebase upstream/master`
- ensure that your `node_modules` directory is not stale by running `yarn install`


To add a new dependency do the following: `yarn add <packagename> --dev`

To update an existing dependency do the following: run `yarn upgrade <packagename>@<version|latest> --dev`
or `yarn upgrade <packagename> --dev` to update to the latest version that matches version constraint
in `package.json`

To Remove an existing dependency do the following: run `yarn remove <packagename>`


Once you've changed the dependency, commit the changes to `package.json` & `yarn.lock`, and you are done.
back to top