From 9970e2872af867bc6663060241c4ed6267215dfd Mon Sep 17 00:00:00 2001 From: David Glasser Date: Fri, 9 May 2025 08:36:38 -0700 Subject: [PATCH] docs: fix `overrides` example in package-json.md The example and further discussion are about `@npm/foo` but the first mention just says `foo`, which might mislead people into thinking `@npm/` is a special syntax rather than just part of the package name. --- docs/lib/content/configuring-npm/package-json.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lib/content/configuring-npm/package-json.md b/docs/lib/content/configuring-npm/package-json.md index e69a867dae51b..0783ba911209a 100644 --- a/docs/lib/content/configuring-npm/package-json.md +++ b/docs/lib/content/configuring-npm/package-json.md @@ -951,7 +951,7 @@ resolution. Published packages may dictate their resolutions by pinning dependencies or using an [`npm-shrinkwrap.json`](/configuring-npm/npm-shrinkwrap-json) file. -To make sure the package `foo` is always installed as version `1.0.0` no matter +To make sure the package `@npm/foo` is always installed as version `1.0.0` no matter what version your dependencies rely on: ```json