-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Bug: file:
resolutions aren't supported
#268
Comments
Hmmm. I didn't try having |
Tried to create a repo but not sure how to repro this one. Could you please make a minimal repro? |
Absolutely! https://github.com/paullewis/repro-rules-js-issue-268 has a |
Sweet. I see the problem now. Thanks for the repro. It's the transitive case. Should be a relatively easy fix. |
Hey there,
If you have
resolutions
in yourpackage.json
like so:And then you have a package that uses – say –
ts-log
(as per the above), like@graphql-codegen/cli
, a build will fail because of the:
in the path.ERROR: app/BUILD.bazel:15:22: //:.aspect_rules_js/node_modules/@graphql-codegen/cli/2.6.4_@types+node@18.0.0/pkg: invalid label ':.aspect_rules_js/node_modules/ts-log/file:local/ts-log/ref' in dict key element: invalid target name '.aspect_rules_js/node_modules/ts-log/file:local/ts-log/ref': target names may not contain ':'
I'm aware #167 was recently fixed, but I'm seeing this in
rules_js-1.0.0-rc.1
which AFAICT was released afterwards.Thanks!
The text was updated successfully, but these errors were encountered: