honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
angular-cn/packages/compiler-cli/src/ngtsc/transform/BUILD.bazel

25 lines
818 B
Python
Raw Normal View History

feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455
2018-04-06 09:53:10 -07:00
load("//tools:defaults.bzl", "ts_library")
style: enforce buildifier lint on CI (#28186) PR Close #28186
2019-01-16 10:19:01 +01:00
package(default_visibility = ["//visibility:public"])
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455
2018-04-06 09:53:10 -07:00
ts_library(
name = "transform",
style: enforce buildifier lint on CI (#28186) PR Close #28186
2019-01-16 10:19:01 +01:00
srcs = ["index.ts"] + glob([
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455
2018-04-06 09:53:10 -07:00
"src/**/*.ts",
]),
deps = [
"//packages/compiler",
feat(ivy): output diagnostics for many errors in ngtsc (#25647) This commit takes the first steps towards ngtsc producing real TypeScript diagnostics instead of simply throwing errors when encountering incorrect code. A new class is introduced, FatalDiagnosticError, which can be thrown by handlers whenever a condition in the code is encountered which by necessity prevents the class from being compiled. This error type is convertable to a ts.Diagnostic which represents the type and source of the error. Error codes are introduced for Angular errors, and are prefixed with -99 (so error code 1001 becomes -991001) to distinguish them from other TS errors. A function is provided which will read TS diagnostic output and convert the TS errors to NG errors if they match this negative error code format. PR Close #25647
2018-08-23 14:34:55 -07:00
"//packages/compiler-cli/src/ngtsc/diagnostics",
refactor(ivy): extract import rewriting into a separate interface (#27998) Currently the ImportManager class handles various rewriting actions of imports when compiling @angular/core. This is required as code compiled within @angular/core cannot import from '@angular/core'. To work around this, imports are rewritten to get core symbols from a particular file, r3_symbols.ts. In this refactoring, this rewriting logic is moved out of the ImportManager and put behind an interface, ImportRewriter. There are three implementers of the interface: * NoopImportRewriter, used for compiling all non-core packages. * R3SymbolsImportRewriter, used when ngtsc compiles @angular/core. * NgccFlatImportRewriter, used when ngcc compiles @angular/core (special logic is needed because ngcc has to rewrite imports in flat bundles differently than in non-flat bundles). This is a precursor to using this rewriting logic in other contexts besides the ImportManager. PR Close #27998
2019-01-08 11:49:58 -08:00
"//packages/compiler-cli/src/ngtsc/imports",
perf(ivy): basic incremental compilation for ngtsc (#29380) This commit introduces a mechanism for incremental compilation to the ngtsc compiler. Previously, incremental information was used in the construction of the ts.Program for subsequent compilations, but was not used in ngtsc itself. This commit adds an IncrementalState class, which tracks state between ngtsc compilations. Currently, this supports skipping the TypeScript emit step when the compiler can prove the contents of emit have not changed. This is implemented for @Injectables as well as for files which don't contain any Angular decorated types. These are the only files which can be proven to be safe today. See ngtsc/incremental/README.md for more details. PR Close #29380
2019-03-18 12:25:26 -07:00
"//packages/compiler-cli/src/ngtsc/incremental",
feat(ivy): setup boilerplate for component indexing API (#30961) Set up the skeleton for a compiler API that indexes components and their templates on an independent indexing step. Part of #30959 PR Close #30961
2019-06-10 09:19:35 -07:00
"//packages/compiler-cli/src/ngtsc/indexer",
feat(ivy): performance trace mechanism for ngtsc (#29380) This commit adds a `tracePerformance` option for tsconfig.json. When specified, it causes a JSON file with timing information from the ngtsc compiler to be emitted at the specified path. This tracing system is used to instrument the analysis/emit phases of compilation, and will be useful in debugging future integration work with @angular/cli. See ngtsc/perf/README.md for more details. PR Close #29380
2019-03-18 11:16:38 -07:00
"//packages/compiler-cli/src/ngtsc/perf",
refactor(ivy): split apart the 'metadata' package in the ngtsc compiler (#27743) This refactoring moves code around between a few of the ngtsc subpackages, with the goal of having a more logical package structure. Additional interfaces are also introduced where they make sense. The 'metadata' package formerly contained both the partial evaluator, the TypeScriptReflectionHost as well as some other reflection functions, and the Reference interface and various implementations. This package was split into 3 parts. The partial evaluator now has its own package 'partial_evaluator', and exists behind an interface PartialEvaluator instead of a top-level function. In the future this will be useful for reducing churn as the partial evaluator becomes more complicated. The TypeScriptReflectionHost and other miscellaneous functions have moved into a new 'reflection' package. The former 'host' package which contained the ReflectionHost interface and associated types was also merged into this new 'reflection' package. Finally, the Reference APIs were moved to the 'imports' package, which will consolidate all import-related logic in ngtsc. PR Close #27743
2018-12-18 09:48:15 -08:00
"//packages/compiler-cli/src/ngtsc/reflection",
feat(ivy): track compilation scope dependencies for components (#30238) To support skipping analysis of a file containing a component we need to know that none of the declarations that might affect its ngtsc compilation have not changed. The files that we need to check are those that contain classes from the `CompilationScope` of the component. These classes are already tracked in the `LocalModuleScopeRegistry`. This commit modifies the `IvyCompilation` class to record the files that are in each declared class's `CompilationScope` via a new method, `recordNgModuleScopeDependencies()`, that is called after all the handlers have been "resolved". Further, if analysis is skipped for a declared class, then we need to recover the analysis from the previous compilation run. To support this, the `IncrementalState` class has been updated to expose the `MetadataReader` and `MetadataRegistry` interfaces. This is included in the `metaRegistry` object to capture these analyses, and also in the `localMetaReader` as a fallback to use if the current compilation analysis was skipped. PR Close #30238
2019-05-08 15:10:50 +01:00
"//packages/compiler-cli/src/ngtsc/scope",
refactor(ivy): move the expr/stmt translator to a separate target (#26203) Template type-checking will make use of expression and statement translation as well as the ImportManager, so this code needs to live in a separate build target which can be depended on by both the main ngtsc transform as well as the template type-checking mechanism. This refactor introduces a separate build target for that code. PR Close #26203
2018-09-21 12:15:06 -07:00
"//packages/compiler-cli/src/ngtsc/translator",
feat(ivy): turn on template type-checking via fullTemplateTypeCheck (#26203) This commit enables generation and checking of a type checking ts.Program whenever the fullTemplateTypeCheck flag is enabled in tsconfig.json. It puts together all the pieces built previously and causes diagnostics to be emitted whenever type errors are discovered in a template. Todos: * map errors back to template HTML * expand set of type errors covered in generated type-check blocks PR Close #26203
2018-09-21 14:03:55 -07:00
"//packages/compiler-cli/src/ngtsc/typecheck",
feat(ivy): ngtsc compiles @Component, @Directive, @NgModule (#24427) This change supports compilation of components, directives, and modules within ngtsc. Support is not complete, but is enough to compile and test //packages/core/test/bundling/todo in full AOT mode. Code size benefits are not yet achieved as //packages/core itself does not get compiled, and some decorators (e.g. @Input) are not stripped, leading to unwanted code being retained by the tree-shaker. This will be improved in future commits. PR Close #24427
2018-05-31 15:50:02 -07:00
"//packages/compiler-cli/src/ngtsc/util",
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 09:54:42 -08:00
"@npm//typescript",
feat(ivy): first steps towards ngtsc mode (#23455) This commit adds a new compiler pipeline that isn't dependent on global analysis, referred to as 'ngtsc'. This new compiler is accessed by running ngc with "enableIvy" set to "ngtsc". It reuses the same initialization logic but creates a new implementation of Program which does not perform the global-level analysis that AngularCompilerProgram does. It will be the foundation for the production Ivy compiler. PR Close #23455
2018-04-06 09:53:10 -07:00
],
)
Reference in New Issue Copy Permalink