From 7181aaf52dd34c68e96a4067890131b73f9baf78 Mon Sep 17 00:00:00 2001 From: Nathan Fritz Date: Mon, 23 Aug 2021 16:08:40 -0700 Subject: [PATCH] removed references to the future in scripts docs --- docs/content/using-npm/scripts.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/content/using-npm/scripts.md b/docs/content/using-npm/scripts.md index 5d57dfe88022b..e033afd30188a 100644 --- a/docs/content/using-npm/scripts.md +++ b/docs/content/using-npm/scripts.md @@ -203,9 +203,11 @@ will default the `start` command to `node server.js`. `prestart` and * `test` * `posttest` -#### [`npm uninstall`](/commands/npm-uninstall) deprecation +#### A Note on a lack of [`npm uninstall`](/commands/npm-uninstall) scripts -While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful. Lifecycle scripts will need to be reworked in the future in order to handle cases such as: +While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a package can happen for a wide variety of reasons, and there's no clear way to currently give the script enough context to be useful. + +Reasons for a package removal include: * a user directly uninstalled this package * a user uninstalled a dependant package and so this dependency is being uninstalled @@ -213,7 +215,7 @@ While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a pa * this version has been merged as a duplicate with another version * etc. -Until these nuances are addressed, `uninstall` lifecycle scripts are not implemented and will not function. +Due to the lack of necessary context, `uninstall` lifecycle scripts are not implemented and will not function. ### User