angular/packages/compiler-cli/ngcc/src/entry_point_finder/interface.ts
Pete Bacon Darwin a581773887 perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)
Previously, ngcc had to walk the entire `node_modules` tree looking for
entry-points, even if it only needed to process a single target entry-point
and its dependencies.

This added up to a few seconds to each execution of ngcc, which is noticeable
when being run via the CLI integration.

Now, if an entry-point target is provided, only that target and its entry-points
are considered rather than the whole folder tree.

PR Close #30525
2019-07-09 09:40:46 -07:00

15 lines
419 B
TypeScript

/**
* @license
* Copyright Google Inc. All Rights Reserved.
*
* Use of this source code is governed by an MIT-style license that can be
* found in the LICENSE file at https://angular.io/license
*/
import {SortedEntryPointsInfo} from '../dependencies/dependency_resolver';
export interface EntryPointFinder {
/**
* Search for Angular package entry-points.
*/
findEntryPoints(): SortedEntryPointsInfo;
}