Prepare for migration from ts_library to ts_project
With the upcoming migration from rules_nodejs to rules_js, I am
changing all the `ts_library` targets to become `ts_project` targets.
This patch introduces an alias for a NOP effect. A future patch will
switch the actual implementation.
I am leaving the scouting directory alone because all the build rules
will change completely. They will use Angular-specific rules.
Signed-off-by: Philipp Schrader <philipp.schrader@gmail.com>
Change-Id: I4b4fd4d14dbf25d6dbdaa3c1725ee6b651eedab6
diff --git a/frc971/image_streamer/www/BUILD b/frc971/image_streamer/www/BUILD
index 908c5b4..f808a73 100644
--- a/frc971/image_streamer/www/BUILD
+++ b/frc971/image_streamer/www/BUILD
@@ -1,5 +1,4 @@
-load("@npm//@bazel/typescript:index.bzl", "ts_library")
-load("//tools/build_rules:js.bzl", "rollup_bundle")
+load("//tools/build_rules:js.bzl", "rollup_bundle", "ts_project")
load("//frc971/downloader:downloader.bzl", "aos_downloader_dir")
package(default_visibility = ["//visibility:public"])
@@ -12,7 +11,7 @@
]),
)
-ts_library(
+ts_project(
name = "proxy",
srcs = [
"proxy.ts",
@@ -23,7 +22,7 @@
],
)
-ts_library(
+ts_project(
name = "main",
srcs = [
"main.ts",