Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/integration/side-effects
History
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
..
snapshots refactor: apply prettier formatting to integration (#54653) 2024-04-02 20:42:04 +00:00
.gitignore test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -07:00
BUILD.bazel build: setup test targets for integration tests with new rule (#44238) 2021-12-08 13:42:41 -05:00
package.json build: remove yarn from integration tests, switch to pnpm (#63902) 2025-09-18 14:39:51 +00:00
pnpm-lock.yaml build: remove yarn from integration tests, switch to pnpm (#63902) 2025-09-18 14:39:51 +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

README.md

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.