honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
eb34aa551a
angular-cn/integration/side-effects
History
Paul Gschwendtner 040253c426 build: update side-effects integration test to not expect esm5 output () 
As mentioned in previous commits, as of v10 the release output
does no longer contain ESM5 output due to an update to the APF.

This means that the side-effect integration test needs to be
updated as it currently expects/tests esm5 output.

PR Close
2020-05-06 13:54:27 -07:00
..
snapshots
build: update side-effects integration test to not expect esm5 output ()
2020-05-06 13:54:27 -07:00
.gitignore
test: add integration test for side effects ()
2019-05-16 12:08:49 -07:00
package.json
test: add integration test for side effects ()
2019-05-16 12:08:49 -07:00
README.md
test: add integration test for side effects ()
2019-05-16 12:08:49 -07:00
side-effects.json
build: update side-effects integration test to not expect esm5 output ()
2020-05-06 13:54:27 -07:00
yarn.lock
feat: typescript 3.6 support ()
2019-10-18 13:15:16 -04: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.