Bazel build rules require npm #7988
Description
After upgrading to v23.5.26, projects importing flatbuffers via Bazel fail if @npm repo isn't present, even if the TS rules aren't in use.
WORKSPACE rule:
http_archive(
name = "com_github_google_flatbuffers",
sha256 = "1cce06b17cddd896b6d73cc047e36a254fb8df4d7ea18a46acf16c4c0cd3f3f3",
strip_prefix = "flatbuffers-23.5.26",
urls = ["https://github.com/google/flatbuffers/archive/refs/tags/v23.5.26.tar.gz"],
)
Build command: bazel build -c opt @com_github_google_flatbuffers//:flatbuffers
Error:
ERROR: Skipping '@com_github_google_flatbuffers//:flatbuffers': error loading package '@com_github_google_flatbuffers//': Unable to find package for @npm//:defs.bzl: The repository '@npm' could not be resolved: Repository '@npm' is not defined.
WARNING: Target pattern parsing failed.
ERROR: error loading package '@com_github_google_flatbuffers//': Unable to find package for @npm//:defs.bzl: The repository '@npm' could not be resolved: Repository '@npm' is not defined.
INFO: Elapsed time: 0.023s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
currently loading: @com_github_google_flatbuffers//
This seems to be a regression as of #7928
@philsc thoughts?