…o explicitly call out `angular.json`

Internally, we've gotten a lot of bugs of users running the CLI in the wrong directory and not understanding this error. Hopefully calling this out more explicitly will key users to double-check their working directory before filing a bug.

(cherry picked from commit f9187bc)

…sion 3

(cherry picked from commit 0323a35)

This option causes our CI to be green even when new projects are created with mismatching TypeScript versions, which causes failures in a real-world project.

See #22333 for more context.

(cherry picked from commit fb3b1fe)

(cherry picked from commit e65a59d)

…structions

In v13.1, we forgot to increment this value and caused an error for early adopters of `13.1.0`. CI should catch this mistake now, and these docs will serve as a reminder to bump the value before release.

(cherry picked from commit 6fdfe97)

Adds a CI tests to verify that we don't merge accident breaking changes

(cherry picked from commit 60036d1)

(cherry picked from commit ecc31f0)

(cherry picked from commit ddec41e)

…specified in `styles` option

This fixes an issue were in some cases when importing CSS in the compilation using import syntax caused CSS to be extracted which causes a runtime error.

In general this is not something that we fully support since this is a specific webpack features and importing CSS as if they were ES modules not supported by the browsers. However, certain widely using libraries such as Monaco editor depend on this specific Webpack feature.

Note: This non-standard unsupported behaviour will no longer be possible in the next major version.

Closes #22358

(cherry picked from commit f1d2873)

… `verbose` option is used

With this change we enabling Webpack to display additional cache related logs when the `verbose` option is enabled. This is helpful to debug cache misses.

(cherry picked from commit 4719300)

… restored

With this change we reduce the redundant module rebuilds when Webpack's FS cache is restored.

Previously, when the cache was restored we caused all modules to be rebuild even though their contents didn't change. This is because the file emit history wasn't persisted to disk.

This also caused the side effect that Webpack will create additional cache `pack` files due to the unnecessary module rebuilds, which ultimatly causes increase of the size of the cache on disk.

(cherry picked from commit b03b9ee)