25bc56ed64
The `setup-local` scripts (and others that are based on it, such as `setup-local-viewengine`), mainly does two things: Replace the Angular packages with the locally built ones for `aio/` and the docs examples (`aio/tools/examples/shared/`). It does this by calling two other npm scripts: `aio-use-local` and `example-use-local` respectively. For these scripts to work, the local Angular packages must be already built (via `scripts/build-packages-dist.sh`). In order to make it easier for people to test against local packages, the scripts support a `--build-packages` option, that (if passed) will result in building the local packages as well. Given that the same local packages are used for both `aio/` and the examples, we only need to build the packages once. Also, to speed up execution on CI, we do not need to build the packages there, because the packages would have been built already in a previous CI job. However, the various setup npm scripts were not implemented correctly to meet these requirements. Specifically, when running locally, `aio-use-local` would build the packages, while `example-use-local` would not (it was supposed to use the already built packages from `aio-use-local`). The `example-use-local` script, though, was configured to run before `aio-use-local`. As a result, the packages were not built, by the time `example-use-local` needed them, which would cause an error. This commit fixes it by ensuring that `aio-use-local` (which builds the local Angular packages) runs before `example-use-local`, so that the latter can use the same packages already built by the former. PR Close #33206
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.