Previously the `ConcreteDeclaration` and `InlineDeclaration` had different properties for the underlying node type. And the `InlineDeclaration` did not store a value that represented its declaration. It turns out that a natural declaration node for an inline type is the expression. For example in UMD/CommonJS this would be the `exports.<name>` property access node. So this expression is now used for the `node` of `InlineDeclaration` types and the `expression` property is dropped. To support this the codebase has been refactored to use a new `DeclarationNode` type which is a union of `ts.Declaration|ts.Expression` instead of `ts.Declaration` throughout. PR Close #38959
21 lines
620 B
Python
21 lines
620 B
Python
load("//tools:defaults.bzl", "ts_library")
|
|
|
|
package(default_visibility = ["//visibility:public"])
|
|
|
|
ts_library(
|
|
name = "entry_point",
|
|
srcs = ["index.ts"] + glob([
|
|
"src/**/*.ts",
|
|
]),
|
|
module_name = "@angular/compiler-cli/src/ngtsc/entry_point",
|
|
deps = [
|
|
"//packages/compiler-cli/src/ngtsc/diagnostics",
|
|
"//packages/compiler-cli/src/ngtsc/file_system",
|
|
"//packages/compiler-cli/src/ngtsc/reflection",
|
|
"//packages/compiler-cli/src/ngtsc/shims:api",
|
|
"//packages/compiler-cli/src/ngtsc/util",
|
|
"@npm//@types/node",
|
|
"@npm//typescript",
|
|
],
|
|
)
|