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
For reference, incase any users hit this is the future, the comment on the rules_js 1.0 npm_translate_lock use_starlark_yaml_parser attribute goes into more detail:
This opt-out is a return safety in cases where yq is not able to parse the pnpm generated
We removed this opt-out to use the Starlark parser in rules_js 2.0 since this is a very rare case that I have not heard of a single report of in the wild. Dropping the old Starlark parser results in a smaller surface area for maintainers of rules_js.
If someone does hit this in the future, the principled fix is in pnpm so that it generates valid yaml that yq can parse.
What happened?
Some pnpm-lockfiles have been known to have invalid yaml causing
yq
to fail, for example:Possible related or caused by pnpm/pnpm#5414.
Previously use_starlark_yaml_parser was provided to workaround such issues. This is removed in rules_js v2.
Version
rules_js v2+
The text was updated successfully, but these errors were encountered: