angular-docs-cn/packages/core/schematics/BUILD.bazel

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

exports_files([
    "tsconfig.json",
    "migrations.json",
])

npm_package(
    name = "npm_package",
    srcs = ["migrations.json"],
    visibility = ["//packages/core:__pkg__"],
    deps = [
        "//packages/core/schematics/migrations/static-queries",
        "//packages/core/schematics/migrations/template-var-assignment",
    ],
)
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983 2019-02-27 14:30:38 -05:00			`load("//tools:defaults.bzl", "npm_package")`

			`exports_files([`
			`"tsconfig.json",`
			`"migrations.json",`
			`])`

			`npm_package(`
			`name = "npm_package",`
			`srcs = ["migrations.json"],`
			`visibility = ["//packages/core:__pkg__"],`
fix(core): add missing migration to npm package (#29705) While running `ng update @angular/core --next`, the following error would be displayed: ``` Cannot find module '....\node_modules\@angular\core\schematics\migrations\template-var-assignment\index' ``` This happened because the Schematics migration was referenced, but not included. This commit fixes that bug by including the migration in the Bazel npm package dependencies. PR Close #29705 2019-04-04 05:18:28 -04:00			`deps = [`
			`"//packages/core/schematics/migrations/static-queries",`
			`"//packages/core/schematics/migrations/template-var-assignment",`
			`],`
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983 2019-02-27 14:30:38 -05:00			`)`