nested_packages rule with targets that don't belong to nested folders #3367
Unanswered
vitorelourenco
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've tried doing that and then run
bazel run //packages/app:pkg.pack
. No errors are thrown and no warnings are given, but the folder isn't copied into the package either. Is this expected behavior and is there a way to achieve this? When using thenpm_pkg
rule on a package that is importing other local packages that aren't nested inside the current package folder, should I simplyrollup
instead of trying to copy and paste dependencies? Does this have to do with module resolution issues? I'm really interested in Bazel so I'm trying to understand how the build system works. Thanks!Beta Was this translation helpful? Give feedback.
All reactions