From 84cdcfb68d5612e58fd66e391b7759f5aa1cf653 Mon Sep 17 00:00:00 2001 From: Vitaly Zdanevich Date: Fri, 17 May 2024 06:42:08 +0300 Subject: [PATCH] Update resolving-eacces-permissions-errors-when-installing-packages-globally.mdx: example improve --- ...ces-permissions-errors-when-installing-packages-globally.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/packages-and-modules/getting-packages-from-the-registry/resolving-eacces-permissions-errors-when-installing-packages-globally.mdx b/content/packages-and-modules/getting-packages-from-the-registry/resolving-eacces-permissions-errors-when-installing-packages-globally.mdx index 42d294f37a2..12544b31108 100644 --- a/content/packages-and-modules/getting-packages-from-the-registry/resolving-eacces-permissions-errors-when-installing-packages-globally.mdx +++ b/content/packages-and-modules/getting-packages-from-the-registry/resolving-eacces-permissions-errors-when-installing-packages-globally.mdx @@ -61,7 +61,7 @@ To minimize the chance of permissions errors, you can configure npm to use a dif Instead of steps 3-5, you can use the corresponding ENV variable (e.g. if you don't want to modify `~/.profile`): ``` -NPM_CONFIG_PREFIX=~/.npm-global +NPM_CONFIG_PREFIX=~/.npm-global npm install -g something ```