You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oad("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "build_bazel_rules_nodejs",
# Replace with a real SHA256 checksum
sha256 = "{SHA256}"
# Replace with a real release version
urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/{VERSION}/rules_nodejs-{VERSION}.tar.gz"],
)
load("@build_bazel_rules_nodejs//:index.bzl", "npm_install")
# Install your declared Node.js dependencies
npm_install(
name = "npm",
package_json = "//:package.json",
yarn_lock = "//:yarn.lock",
)
load(
"@io_bazel_rules_docker//repositories:repositories.bzl",
container_repositories = "repositories",
)
container_repositories()
load(
"@io_bazel_rules_docker//nodejs:image.bzl",
_nodejs_image_repos = "repositories",
)
_nodejs_image_repos()
Is this a regression?
Yes, the previous version in which this bug was not present was: ....
Description
🔬 Minimal Reproduction
bazel clean --expunge && bazel sync
🔥 Exception or Error
renguizhou@renguidembp backend % bazel clean --expunge && bazel sync
Starting local Bazel server and connecting to it...
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
Starting local Bazel server and connecting to it...
ERROR: ErrorInfo{exception=null, cycles=[[] -> [[/Users/renguizhou/Desktop/haystack/zaplink/backend]/[WORKSPACE.bazel], 2, KeyForWorkspace{label=@build_bazel_rules_nodejs//:index.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@build_bazel_rules_nodejs//internal/pkg_web:pkg_web.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@rules_nodejs//nodejs:providers.bzl, isBuildPrelude=false}, CONTAINING_PACKAGE_LOOKUP:@rules_nodejs//nodejs, PACKAGE_LOOKUP:@rules_nodejs//nodejs, REPOSITORY_DIRECTORY:@rules_nodejs]], isCatastrophic=false, isDirectlyTransient=false, isTransitivelyTransient=false}
checking cached actions
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!
🐞 bug report
Affected Rule
The issue is caused by the rule:WORKPSACE.bazel
Is this a regression?
Yes, the previous version in which this bug was not present was: ....Description
🔬 Minimal Reproduction
bazel clean --expunge && bazel sync
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_docker version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: