3 Matching Annotations
  1. Jan 2019
    1. So it realizes that clean is a dependency of two tasks. In this way, it makes sure that it is executed only once.

      gulp3.0 traces the dependencies and generates the dependency tree such that it only executes a common dependency once.

    2. Imagine triggering the styles task every time you change one of your CSS files. It would execute first clean, and then styles, practically deleting your efforts from “script”.

      This means the dependency graph can cause undesirable wipes of a build directory resulting in unnecessary rebuilds.

    3. All those tasks are executed for maximum concurrency.

      If it can, when generating the dependency graph, it will execute dependencies in parallel.