angular / angular-cli Public

Typo in underscore function code documentation.

Renovate supports use hashed version pinning for individual Github actions while still following SemVer-based tags.
All workflow actions external to the Angular organization now leverage this support to ensure both that stable versions of the actions are used and that the actions are pinned to a hashed version of the tag.

…name

When using the unsupported `webpackChunkName` magic comment we renamed the chunk which in some cases causes a runtime error.

Closes #22525

Updates the snapshot e2e setup to reflect the builds repository rename
where `material2-builds` got renamed to `material-builds`.

The `common-tags` development dependency was only used in several E2E tests.
Removing the usage of the dependency also allows it to be removed as a development dependency from the root `package.json`.

The following development dependencies are no longer used directly and have been removed from the root `package.json`:
* `conventional-commits-parser`
* `gh-got`
* `git-raw-commits`

Update bazel to the latest stable version (currently 5.0.0).

Improvements to the framework for `14.0.0-next.3` resulted in reduced main bundle sizes.

```
  Initial Chunk Files           | Names         |  Raw Size | Estimated Transfer Size
  main.f6e8bb94b78b0b43.js      | main          | 120.24 kB |                36.23 kB
```

This is a fix to avoid hosting issues which causes bazel test to fail.

7.17.3 is breaking vendor sourcemaps in windows.

See: https://app.circleci.com/pipelines/github/angular/angular-cli/20692/workflows/9fc4f39e-d2f2-47c3-af01-f3a01c1bf542/jobs/288690

Related to babel/babel#14277

The Dockerfile at the root of the repository is both outdated (uses Node.js v10) and unused by current development processes.

The `seedrandom` dependency is not currently used within the package or project.
As a result, it has been removed to prevent unneeded packages from being installed during development.

…zer package

This API golden file is no longer needed as the `@angular-devkit/build-optimizer` package has been removed as of v14.

The currently recommended best practice for Github action workflows is to set top-level permissions to read only. And if the job uses the automatic `GITHUB_TOKEN`, fine-grained permissions for each job based on the job's requirements should also be added.
All existing workflows in the repository now have top-level read only permission blocks.
Only the `scorecard` workflow currently requires additional job level permissions and the minimum set of permissions were already present for the job.

This is redundant since this is covered by https://github.com/angular/angular-cli/blob/e4e15058cb7a3612cb6ac31cda175783042c5a1c/packages/angular/cli/lib/cli/index.ts#L26