diff --git a/docs/npm_translate_lock.md b/docs/npm_translate_lock.md
index 7c0411360..bede3b382 100644
--- a/docs/npm_translate_lock.md
+++ b/docs/npm_translate_lock.md
@@ -68,7 +68,7 @@ npm_translate_lock(name, external_repository_action_cache, link_workspace, pnpm_version, use_pnpm,
register_copy_directory_toolchains, register_copy_to_directory_toolchains,
register_yq_toolchains, register_tar_toolchains, npm_package_target_name,
- use_starlark_yaml_parser, package_json, warn_on_unqualified_tarball_url, kwargs)
+ use_starlark_yaml_parser, package_json, kwargs)
Repository macro to generate starlark code from a lock file.
@@ -139,7 +139,6 @@ For more about how to use npm_translate_lock, read [pnpm and rules_js](/docs/pnp
| npm_package_target_name | The name of linked `npm_package` targets. When `npm_package` targets are linked as pnpm workspace packages, the name of the target must align with this value.
The `{dirname}` placeholder is replaced with the directory name of the target.
By default the directory name of the target is used.
Default: `{dirname}` | `"{dirname}"` |
| use_starlark_yaml_parser | Opt-out of using `yq` to parse the pnpm-lock file which was added in https://github.com/aspect-build/rules_js/pull/1458 and use the legacy starlark yaml parser instead.
This opt-out is a return safety in cases where yq is not able to parse the pnpm generated yaml file. For example, this has been observed to happen due to a line such as the following in the pnpm generated lock file:
resolution: {tarball: https://gitpkg.vercel.app/blockprotocol/blockprotocol/packages/%40blockprotocol/type-system-web?6526c0e}
$ yq pnpm-lock.yaml -o=json
Error: bad file 'pnpm-lock.yaml': yaml: line 7129: did not find expected ',' or '}'