From 94bb0c3c0df4965783428444e09f3a47575abd5e Mon Sep 17 00:00:00 2001 From: "rahul.puttireddy" Date: Wed, 8 Nov 2023 17:23:49 +0100 Subject: [PATCH] fix postinstall docs --- .../docs/advanced/02-package-management/lifecycle-scripts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docusaurus/docs/advanced/02-package-management/lifecycle-scripts.md b/packages/docusaurus/docs/advanced/02-package-management/lifecycle-scripts.md index aa319b4a1a81..da601527ee5f 100644 --- a/packages/docusaurus/docs/advanced/02-package-management/lifecycle-scripts.md +++ b/packages/docusaurus/docs/advanced/02-package-management/lifecycle-scripts.md @@ -38,7 +38,7 @@ It is guaranteed to be called in topological order (in other words, your depende For backwards compatibility, the `preinstall` and `install` scripts, if presents, are called right before running the `postinstall` script from the same package. In general, prefer using `postinstall` over those two. :::caution -Postinstall scripts have should be avoided at all cost, as they make installs slower and riskier. Many users will refuse to install dependencies that have `postinstall` scripts. Additionally, since the output isn't shown out of the box, using them to print a message to the user will not work as you expect. +Postinstall scripts should be avoided at all cost, as they make installs slower and riskier. Many users will refuse to install dependencies that have `postinstall` scripts. Additionally, since the output isn't shown out of the box, using them to print a message to the user will not work as you expect. ::: ## Environment variables