devtools/projects/ng-devtools-backend/BUILD.bazel

load("@build_bazel_rules_nodejs//:index.bzl", "js_library")
load("//devtools/tools:typescript.bzl", "ts_library")

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

ts_library(
    name = "ng_devtools_backend_ts",
    srcs = ["index.ts"],
    deps = [
        "//devtools/projects/ng-devtools-backend/src",
    ],
)

js_library(
    name = "ng-devtools-backend",
    package_name = "ng-devtools-backend",
    deps = [":ng_devtools_backend_ts"],
)
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests. 2021-11-07 18:57:52 -05:00			`load("@build_bazel_rules_nodejs//:index.bzl", "js_library")`
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00			`load("//devtools/tools:typescript.bzl", "ts_library")`
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests. 2021-11-07 18:57:52 -05:00
build(devtools): migrate ng-devtools-backend to bazel Allows the ng-devtools-backend to be built with bazel. Allows ng-devtools-backend to be used as a dependency in other bazel build rules. 2021-09-08 18:36:40 -04:00			`package(default_visibility = ["//visibility:public"])`

refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00			`ts_library(`
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in. 2021-12-09 03:41:40 -05:00			`name = "ng_devtools_backend_ts",`
build(devtools): migrate ng-devtools-backend to bazel Allows the ng-devtools-backend to be built with bazel. Allows ng-devtools-backend to be used as a dependency in other bazel build rules. 2021-09-08 18:36:40 -04:00			`srcs = ["index.ts"],`
			`deps = [`
refactor(devtools): bring the angular devtools directory into the root bazel workspace Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. 2021-12-16 02:00:43 -05:00			`"//devtools/projects/ng-devtools-backend/src",`
build(devtools): migrate ng-devtools-backend to bazel Allows the ng-devtools-backend to be built with bazel. Allows ng-devtools-backend to be used as a dependency in other bazel build rules. 2021-09-08 18:36:40 -04:00			`],`
			`)`
build(devtools): port over bazel tooling from angular/components Previously the ts_library bazel rule was used to build angular devtools. This commit migrates to ts project and brings in some bazel tooling from angular/components to run bundle spec files for karma tests. 2021-11-07 18:57:52 -05:00
			`js_library(`
			`name = "ng-devtools-backend",`
			`package_name = "ng-devtools-backend",`
refactor(devtools): make bazel labels follow snake case convention Previously, camel case was used for bazel labels in the devtools directory. This commit changes these labels to snake case except in the case where the label is identical to the directory name that the BUILD file is in. 2021-12-09 03:41:40 -05:00			`deps = [":ng_devtools_backend_ts"],`
refactor(devtools): run buildifier on bazel files 2021-11-21 18:19:47 -05:00			`)`