angular/integration/side-effects
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
..
snapshots refactor: apply prettier formatting to integration (#54653) 2024-04-02 20:42:04 +00:00
.gitignore
BUILD.bazel
package.json build: update pnpm to v10.19.0 (#64606) 2025-10-23 12:37:04 +02:00
pnpm-lock.yaml build: lock file maintenance (#64533) 2025-10-20 16:03:34 +00:00
pnpm-workspace.yaml build: remove yarn from integration tests, switch to pnpm (#63902) 2025-09-18 14:39:51 +00:00
README.md build: remove yarn from integration tests, switch to pnpm (#63902) 2025-09-18 14:39:51 +00:00
side-effects.json feat(bazel): (APF) Angular Package Format updates (#49559) 2023-03-23 08:18:45 -07:00

This test checks if the side effects for loading Angular packages have changed using https://github.com/filipesilva/check-side-effects.

Running pnpm test will check all ES modules listed in side-effects.json.

Running pnpm update will update any changed side effects.

To add a new ES module to this test, add a new entry in side-effects.json.

Usually the ESM and FESM should have the same output, but retained objects that were renamed during the flattening step will leave behind a different name.