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 1
angular/integration/side-effects
History
Paul Gschwendtner 63673ddd3f build: re-add lock files for integration tests (#49787) 
The lock files for integration tests have been accidentally
removed with: 612eaca3c5

This commit re-adds them.

PR Close #49787
2023-04-11 10:26:42 -07:00
..
snapshots feat(bazel): (APF) Angular Package Format updates (#49559) 2023-03-23 08:18:45 -07: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 test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -07:00
README.md test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -07:00
side-effects.json feat(bazel): (APF) Angular Package Format updates (#49559) 2023-03-23 08:18:45 -07:00
yarn.lock build: re-add lock files for integration tests (#49787) 2023-04-11 10:26:42 -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 yarn test will check all ES modules listed in side-effects.json.

Running yarn 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.