Commit graph

14 commits

Author SHA1 Message Date
Angular Robot
2922b411e5 build: update pnpm to v10.20.0
See associated pull request for more information.
2025-10-31 22:15:02 +00:00
Angular Robot
07a6379de4 build: update pnpm to v10.19.0 (#64606)
See associated pull request for more information.

PR Close #64606
2025-10-23 12:37:04 +02:00
Angular Robot
7572a272a8 build: update pnpm to v10.18.3 (#64431)
See associated pull request for more information.

PR Close #64431
2025-10-15 10:44:22 -07:00
Angular Robot
84f6e36e19 build: update pnpm to v10.18.2 (#64358)
See associated pull request for more information.

PR Close #64358
2025-10-13 08:42:16 -07:00
Angular Robot
a15688c2da build: update pnpm to v10.18.1 (#64264)
See associated pull request for more information.

PR Close #64264
2025-10-07 20:24:42 -04:00
Angular Robot
da0982a5fd build: update pnpm to v10.18.0 (#64232)
See associated pull request for more information.

PR Close #64232
2025-10-06 14:57:16 -04:00
Angular Robot
f36a5049b5 build: update pnpm to v10.17.1 (#64015)
See associated pull request for more information.

PR Close #64015
2025-09-23 21:40:03 +00:00
Alan Agius
00a1f99e8d test: update integration test dependencies (#63937)
During a previous PR review, it was noted that the `next` tag was causing confusion. This commit updates the dependencies for the integration tests to resolve this ambiguity and ensure clarity going forward.

Additionally, this change uses the `link:` protocol to ensure that `pnpm i` does not fail when lockfiles or dependencies are updated outside of Bazel.

PR Close #63937
2025-09-19 14:38:42 +00:00
Alan Agius
950ffd001e build: remove yarn from integration tests, switch to pnpm (#63902)
This commit removes Yarn as a package manager for integration tests and migrates to pnpm. This change aims to standardize package management across the project, leveraging pnpm's efficiency and consistent behavior for dependency resolution and installation.

PR Close #63902
2025-09-18 14:39:51 +00:00
Joey Perrott
50c7e132b5 test: use zone from npm instead of the locally built package for integration tests (#61947)
Use zone from npm for integration tests

PR Close #61947
2025-06-06 15:20:11 -07:00
JiaLiPassion
d37939623f test(zone.js): test zone.js package with tgz (#38649)
Zone.js 0.11.0 release an empty bundle, and now the npm_package tests all target
bazel rule `npm_package`, but not `npm_package.pack`, and these two rules may
generate different results, for example, Zone.js 0.11.0's issue is `package.json`
define files array which make the bundle only include the files in the files array.
So this PR install the zone.js package from the archive generated from `npm_package.pack` rule.

PR Close #38649
2020-10-19 08:06:11 -07:00
George Kalpakas
74b7d1ace1 test(ngcc): build zone.js from source in scripts/build-packages-dist.sh (#33733)
In #33046, internal uses of `zone.js` were switched to reference it
directly from source (built with Bazel) instead of npm. As a result, the
necessary scripts were updated to build `zone.js` as necessary. However,
some `integration/**/debug-test.sh` scripts were missed (apparently
because they are not used on CI, but only locally as helpers for
debugging the integration projects).

This commit updates the `scripts/build-packages-dist.sh` script to also
build `zone.js`, so that other scripts (such as the various
`debug-test.sh` scripts) can use it.

PR Close #33733
2019-11-12 09:55:16 -08:00
JiaLiPassion
8c6fb17d29 build: reference zone.js from source directly instead of npm. (#33046)
Close #32482

PR Close #33046
2019-11-06 00:48:34 +00:00
George Kalpakas
84f3dfbca4 test(service-worker): verify that config/schema.json is published to npm (#27859)
PR Close #27859
2019-03-05 16:48:26 -08:00