Generated webpack rule doesn't build when used as a dependency #3257
Description
🐞 bug report
Affected Rule
The issue is caused by the rule:@npm//webpack
Is this a regression?
Not sure, this is my first attempt with Bazel + JSDescription
A clear and concise description of the problem...Please take a look at the minimal repro below. I have two rules. The first uses @npm//webpack to bundle JS files, and the second is a sh_binary rule that uses the output of the first as data attribute. Running bazel query 'deps(//:upload)' correctly shows that //:src/index.js is a dependency (along with a lot of node modules files).
When I bazel build //:upload, the build completes without error, but webpack is not invoked. Checking bazel-out and bazel-bin confirms that there is no webpack output.
🔬 Minimal Reproduction
https://github.com/geoffliu/bazel-issue
🔥 Exception or Error
None
🌍 Your Environment
Operating System:
OSX 11.6
Output of bazel version:
Build label: 4.2.2-homebrew
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Jan 1 00:00:00 1980 (315532800)
Build timestamp: 315532800
Build timestamp as int: 315532800
Rules_nodejs version:
(Please check that you have matching versions between WORKSPACE file and @bazel/* npm packages.)
4.6.0
Anything else relevant?