And it failed as expected, printing out the circular dependencies:

Starting 'build/checkCircularDependencies'...
[ [ 'angular2/src/core/compiler/element_binder',
    'angular2/src/core/compiler/view' ],
  [ 'angular2/src/core/compiler/pipeline/compile_control',
    'angular2/src/core/compiler/pipeline/compile_element',
    'angular2/src/core/compiler/element_binder',
    'angular2/src/core/compiler/view',
    'angular2/src/core/compiler/shadow_dom_strategy' ],
  [ 'angular2/src/core/compiler/pipeline/compile_element',
    'angular2/src/core/compiler/element_binder',
    'angular2/src/core/compiler/view',
    'angular2/src/core/compiler/shadow_dom_strategy' ] ]

@Mlaval This seems to be working, but I am not sure how it should be used.

When I run gulp build/checkCircularDependencies I see a list of cyclic dependencies. But when I run build.js.dev, I see no errors. Can you explain what this is for and how it works?

@vsavkin the build/checkCircularDependencies task only scans the /dist/js/dev/es6/ folder to find out circular dependencies, using Madge and ignoring the import * as .... It it finds some, it logs them and exits immediately.
It does not rebuild the /dist/js/dev/es6/ folder.

So my guess is that you ran the task with some old code in this folder, hence you got the list. Then, when you ran build.js.dev, it generated a fresh /dist/js/dev/es6/ where there was no more issues.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}