angular-cn/packages/compiler-cli/src/ngtsc/util/BUILD.bazel

package(default_visibility = ["//visibility:public"])

load("//tools:defaults.bzl", "ts_library")

ts_library(
    name = "util",
    srcs = glob([
        "src/**/*.ts",
    ]),
    module_name = "@angular/compiler-cli/src/ngtsc/util",
    deps = [
        "//packages:types",
        "@ngdeps//@types/node",
        "@ngdeps//canonical-path",
        "@ngdeps//typescript",
    ],
)
feat(ivy): a generic visitor which allows prefixing nodes for ngtsc (#24230) This adds ngtsc/util/src/visitor, a utility for visiting TS ASTs that can add synthetic nodes immediately prior to certain types of nodes (e.g. class declarations). It's useful to lift definitions that need to be referenced repeatedly in generated code outside of the class that defines them. PR Close #24230 2018-05-30 16:02:53 -07:00			`package(default_visibility = ["//visibility:public"])`

			`load("//tools:defaults.bzl", "ts_library")`

			`ts_library(`
			`name = "util",`
			`srcs = glob([`
			`"src/*/.ts",`
			`]),`
			`module_name = "@angular/compiler-cli/src/ngtsc/util",`
feat(ivy): able to compile @angular/core with ngtsc (#24677) @angular/core is unique in that it defines the Angular decorators (@Component, @Directive, etc). Ordinarily ngtsc looks for imports from @angular/core in order to identify these decorators. Clearly within core itself, this strategy doesn't work. Instead, a special constant ITS_JUST_ANGULAR is declared within a known file in @angular/core. If ngtsc sees this constant it knows core is being compiled and can ignore the imports when evaluating decorators. Additionally, when compiling decorators ngtsc will often write an import to @angular/core for needed symbols. However @angular/core cannot import itself. This change creates a module within core to export all the symbols needed to compile it and adds intelligence within ngtsc to write relative imports to that module, instead of absolute imports to @angular/core. PR Close #24677 2018-06-20 15:54:16 -07:00			`deps = [`
			`"//packages:types",`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`"@ngdeps//@types/node",`
fix(ivy): correct ngtsc path handling in Windows (#26703) As it turns out, the usage of path.posix does not unify path handling across operating systems. Instead, canonical-path is used to ensure path handling is consistent, avoiding incorrect paths in Windows. See https://github.com/angular/angular/pull/25862#discussion_r216157914 PR Close #26703 2018-10-24 18:39:29 +02:00			`"@ngdeps//canonical-path",`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 13:14:14 -07:00			`"@ngdeps//typescript",`
feat(ivy): able to compile @angular/core with ngtsc (#24677) @angular/core is unique in that it defines the Angular decorators (@Component, @Directive, etc). Ordinarily ngtsc looks for imports from @angular/core in order to identify these decorators. Clearly within core itself, this strategy doesn't work. Instead, a special constant ITS_JUST_ANGULAR is declared within a known file in @angular/core. If ngtsc sees this constant it knows core is being compiled and can ignore the imports when evaluating decorators. Additionally, when compiling decorators ngtsc will often write an import to @angular/core for needed symbols. However @angular/core cannot import itself. This change creates a module within core to export all the symbols needed to compile it and adds intelligence within ngtsc to write relative imports to that module, instead of absolute imports to @angular/core. PR Close #24677 2018-06-20 15:54:16 -07:00			`],`
feat(ivy): a generic visitor which allows prefixing nodes for ngtsc (#24230) This adds ngtsc/util/src/visitor, a utility for visiting TS ASTs that can add synthetic nodes immediately prior to certain types of nodes (e.g. class declarations). It's useful to lift definitions that need to be referenced repeatedly in generated code outside of the class that defines them. PR Close #24230 2018-05-30 16:02:53 -07:00			`)`