a581773887
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
48 lines
1.5 KiB
JSON
48 lines
1.5 KiB
JSON
{
|
|
"compilerOptions": {
|
|
"baseUrl": ".",
|
|
"declaration": true,
|
|
"experimentalDecorators": true,
|
|
"emitDecoratorMetadata": true,
|
|
"module": "commonjs",
|
|
"moduleResolution": "node",
|
|
"strictNullChecks": true,
|
|
"strictPropertyInitialization": true,
|
|
"outDir": "../dist/all/@angular",
|
|
"noImplicitAny": true,
|
|
"noFallthroughCasesInSwitch": true,
|
|
"paths": {
|
|
"selenium-webdriver": ["../node_modules/@types/selenium-webdriver/index.d.ts"],
|
|
"rxjs/*": ["../node_modules/rxjs/*"],
|
|
"@angular/*": ["./*"],
|
|
"e2e_util/*": ["../modules/e2e_util/*"]
|
|
},
|
|
"rootDir": ".",
|
|
"inlineSourceMap": true,
|
|
"lib": ["es5", "dom", "es2015.promise", "es2015.collection", "es2015.iterable", "es2015.core", "es2017.object"],
|
|
"skipDefaultLibCheck": true,
|
|
"skipLibCheck": true,
|
|
"target": "es5",
|
|
"types": ["angular"]
|
|
},
|
|
"bazelOptions": {
|
|
"suppressTsconfigOverrideWarnings": true
|
|
},
|
|
"exclude": [
|
|
"bazel",
|
|
"common/locales",
|
|
"compiler-cli/integrationtest",
|
|
"core/schematics",
|
|
"elements/schematics",
|
|
// Do not build the example e2e spec files since those require custom typings and
|
|
// aren't required to build all packages.
|
|
"examples/**/e2e_test/*",
|
|
// Exclude the "main.ts" files for each example group because this file is used by
|
|
// Bazel to launch the devserver and uses AOT compilation.
|
|
"examples/**/main.ts",
|
|
"platform-server/integrationtest",
|
|
"router/test/aot_ngsummary_test",
|
|
"zone.js"
|
|
]
|
|
}
|