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
It'd certainly be nice if @npm//bar in this example could be resolved in some way without explictly listing it twice.
But im not sure what the best approach would be.
Describe alternatives you've considered
You can use course-grained deps, or list all subdependencies of a local package
The text was updated successfully, but these errors were encountered:
🚀 feature request
#232 Related
Relevant Rules
nodejs_binary
Description
Consider a repo:
Service A depends on @npm//foo and Package B;
Package B depends on @npm//bar
service-a:binary :
package-b:bundle, has a bunch of rules that output a tree something like
the module resolver is now unable to resolve @npm//bar for any modules in package-b, they must be explictly listed as deps in service-a.
Describe the solution you'd like
It'd certainly be nice if @npm//bar in this example could be resolved in some way without explictly listing it twice.
But im not sure what the best approach would be.
Describe alternatives you've considered
You can use course-grained deps, or list all subdependencies of a local package
The text was updated successfully, but these errors were encountered: