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
{{ message }}
This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Cannot build node_binary depending on firebase module. #62
_bin/build-runfiles (args bazel-out/k8-fastbuild/bin/cedar/backend/run.runfiles_manifest bazel-out/k8-fastbuild/bin/cedar/backend/run.runfiles): link or target filename contains space on line 6: 'toktok/cedar/backend/run_files/node_modules/@firebase/app/coverage/browser/HeadlessChrome 0.0.0 (Linux 0.0.0)/lcov.info /usr/local/home/iphy/.cache/bazel/_bazel_iphy/87c462f2b35b8d3dfe6f6c21308fd127/execroot/toktok/bazel-out/k8-fastbuild/bin/cedar/backend/run_files/node_modules/@firebase/app/coverage/browser/HeadlessChrome 0.0.0 (Linux 0.0.0)/lcov.info'
Wondering what the transitive dependency chain from firebase to headless chrome is. Clearly one does not actually need headless chrome to use the firebase node api. It may be a bug or design flaw in rules_node that puts the headless chrome dependency in _all_.
As a workaround, I'd try naming the deps more narrowly than _all_. You can query the available ones via bazel query @yarn_firebase//:* or less $(bazel info output_base)/external/yarn_firebase/BUILD.bazel
Activity
iphydf commentedon Feb 18, 2018
_bin/build-runfiles (args bazel-out/k8-fastbuild/bin/cedar/backend/run.runfiles_manifest bazel-out/k8-fastbuild/bin/cedar/backend/run.runfiles): link or target filename contains space on line 6: 'toktok/cedar/backend/run_files/node_modules/@firebase/app/coverage/browser/HeadlessChrome 0.0.0 (Linux 0.0.0)/lcov.info /usr/local/home/iphy/.cache/bazel/_bazel_iphy/87c462f2b35b8d3dfe6f6c21308fd127/execroot/toktok/bazel-out/k8-fastbuild/bin/cedar/backend/run_files/node_modules/@firebase/app/coverage/browser/HeadlessChrome 0.0.0 (Linux 0.0.0)/lcov.info'
pcj commentedon Feb 18, 2018
Known issue: bazelbuild/bazel#374
Wondering what the transitive dependency chain from firebase to headless chrome is. Clearly one does not actually need headless chrome to use the firebase node api. It may be a bug or design flaw in rules_node that puts the headless chrome dependency in
_all_.As a workaround, I'd try naming the deps more narrowly than
_all_. You can query the available ones viabazel query @yarn_firebase//:*orless $(bazel info output_base)/external/yarn_firebase/BUILD.bazel