[Bug]: npm_translate_lock
's update_pnpm_lock
attribute + bzlmod errors on first build when used with external repositories (eg. rules_ts
)
#1371
Labels
bug
Something isn't working
What happened?
I'm trying out
rules_js
'snpm.translate_lock()
withupdate_pnpm_lock
working with withrules_ts()
+bzlmod
I'm finding that the first time I try to execute something like
bazel build //...
with a blankpnpm-lock.yaml
file, thepnpm-lock.yaml
file gets updated, but then theBUILD.bazel
file isn't able to resolve the generatednode_modules
label.On subsequent executions or if there's no need to update the pnpm-lock file, everything is able to resolve & build successfully.
I also tested this using an e2e example in the
rules_ts
repository and see the same result:The failing output and subsequent execution passing output (no changes in between):
Version
Development (host) and target OS/architectures:
Output of
bazel --version
: bazel 6.3.2Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:Language(s) and/or frameworks involved:
TS
How to reproduce
rules_ts
repository:pnpm-lock.yaml
file:The text was updated successfully, but these errors were encountered: