commit | 60fb280a9190be3bff2bad7c64302b9aa5a4b765 | [log] [tgz] |
---|---|---|
author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Thu Jun 02 20:14:36 2022 +0000 |
committer | GitHub <noreply@github.com> | Thu Jun 02 20:14:36 2022 +0000 |
tree | 77b75ee2c0b68bc9ba01df3019c71adeb8525bf2 | |
parent | e048f09dce40e0dd50e7dbc4569d2d7458940cba [diff] |
Bump @angular/core from 4.4.5 to 11.0.5 Bumps [@angular/core](https://github.com/angular/angular/tree/HEAD/packages/core) from 4.4.5 to 11.0.5. - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/11.0.5/packages/core) --- updated-dependencies: - dependency-name: "@angular/core" dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
npm i
npm run dev
npm run checkLicenses
npm run runProd
. This is only to test if AOT is working and should never be used in a production environment.npm run build
. Files will be stored under /dist.npm run test
The version numbers follow the Semantic Versioning scheme.
In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.
The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:
1.2.3-snapshot
1.3.5-m.1
1.5.7-rc.2
2.0.0-ga
See CONTRIBUTING file.
See LICENSE file.