Skip to content

Conversation

mohd-akram
Copy link
Contributor

Simplify the steps a bit:

  • Backing up the computer and creating the directory is not necessary, since it's created automatically by npm.
  • Use the ~/.local directory which is the standard place for user-specific software, and likely to already be in the user's PATH.
  • export is not needed since PATH is already exported.
  • Add a note for zsh which doesn't use ~/.profile.
  • Use a different package as an example, since jshint is not regularly updated, and linters should generally be in devDependencies and used through npm scripts.
  • Ensure the user can run the installed tool.
  • Remove mention of NPM_CONFIG_PREFIX which is not sufficient, since the PATH still needs to be updated to use global tools.
@mohd-akram mohd-akram requested review from a team and leobalter as code owners September 13, 2025 08:00
@owlstronaut owlstronaut self-requested a review September 15, 2025 17:04
@owlstronaut owlstronaut self-assigned this Sep 15, 2025
@owlstronaut owlstronaut merged commit 8c1b9ca into npm:main Sep 15, 2025
8 of 9 checks passed
@mohd-akram mohd-akram deleted the update-permissions-doc branch September 16, 2025 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants