-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build node_binary depending on firebase module. #62
Comments
_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' |
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 As a workaround, I'd try naming the deps more narrowly than |
WORKSPACE:
BUILD: any node_binary with
deps = ["@yarn_firebase//:_all_"]
.The text was updated successfully, but these errors were encountered: