-
Notifications
You must be signed in to change notification settings - Fork 519
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
name 'json' is not defined #2938
Comments
Hey there. Problem is that you are running an old version of bazel which we don’t test against. Could you upgrade your bazel installation and try again? |
@thesayyn - Let me give that a try. |
note that we do have some error checking for this case |
@alexeagle @thesayyn - Thanks a lot! Updating bazel to 4.2.1 resolved this issue for me. Closing the issue. |
🐞 bug report
Affected Rule
The issue is caused by the rule: `npm_install`Is this a regression?
Yes, the previous version in which this bug was not present was: 3.0.0Description
On updating rules_nodejs to version 4.1.0, I'm unable to build anything.
I even tried clearing the
bazel clean --expunge
and alsorm -rf ~/.cache/bazel
but still faced this issue.🔬 Minimal Reproduction
Simply setting up the following code in the
WORKSPACE
and runningbazel sync
I was able to reproduce the issue🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_nodejs version:
The text was updated successfully, but these errors were encountered: