honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/integration/side-effects
History
Miško Hevery f3c69e7f6b refactor(ivy): rewrite flatten function to be more memory efficient (#30468) 
The `flatten` function used `concat` and `slice` which created a lot of intermediary
object allocations. Because `flatten` is used from query any benchmark which
used query would exhibit high minor GC counts.

PR Close #30468
 		2019-05-21 13:06:23 -07:00
..
snapshots refactor(ivy): rewrite flatten function to be more memory efficient (#30468) 2019-05-21 13:06:23 -07:00
.gitignore 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
package.json test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -07:00
side-effects.json test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -07:00
yarn.lock test: add integration test for side effects (#29329) 2019-05-16 12:08:49 -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.