diff --git a/node.js/best-practices.md b/node.js/best-practices.md
index ce2c0cbf6..424c00840 100644
--- a/node.js/best-practices.md
+++ b/node.js/best-practices.md
@@ -77,7 +77,7 @@ Therefore, the rules when publishing packages for reuse are:
 * **Do** an *npm update* before publishing and test thoroughly.
   (→ ideally automated in your CI/CD pipeline).
 * **Do** the vulnerability checks for your software and all open-source software used by you **or by packages you used** (→ [Minimize Usage of Open Source Packages](#oss)).
-* **Don't** do `npm shrinkwrap` → see also [npm's docs](https://docs.npmjs.com/cli/v7/configuring-npm/npm-shrinkwrap-json): *"It's discouraged for library authors to publish this file, ..."*
+* **Don't** do `npm shrinkwrap` → see also [npm's docs](https://docs.npmjs.com/cli/v10/configuring-npm/npm-shrinkwrap-json): *"It's discouraged for library authors to publish this file, ..."*
 
 ::: tip
 If both your package and a consuming package reuse the same CDS models, loading those models would fail because it's impossible to automatically merge the two versions, nor is it possible to load two independent versions. The reason for this is that it's reusing models that share the **same** single definitions.