NPM-SET(1)

πŸ’– NPM-SET(1) β€” the npm-set glow-up πŸ’–

🌸 NAME 🌸

npm-set β€” Set a value in the npm configuration. That's the whole assignment, bestie. πŸ’…

πŸ¦‹ Synopsis πŸ¦‹

npm set <key>=<value> [<key>=<value> ...] (See `npm config`)
πŸ“ Note: This command is unaware of workspaces. Not me being dramatic, it literally just doesn't know them. πŸ™ˆ

πŸŽ€ Description πŸŽ€

Set a value in the npm configuration. Iconic, simple, to the point. ✨

πŸ’… Configuration πŸ’…

These are the config knobs this page is serving up. 🫢

🌟 global 🌟

  • Default: false
  • Type: Boolean

Operates in "global" mode, so that packages are installed into the prefix folder instead of the current working directory. See npm help folders for more on the differences in behavior.

  • packages are installed into the {prefix}/lib/node_modules folder, instead of the current working directory.
  • bin files are linked to {prefix}/bin
  • man pages are linked to {prefix}/share/man

🌈 location 🌈

  • Default: "user" unless --global is passed, which will also set this value to "global"
  • Type: "global", "user", or "project"

When passed to npm config this refers to which config file to use.

When set to "global" mode, packages are installed into the prefix folder instead of the current working directory. See npm help folders for more on the differences in behavior.

  • packages are installed into the {prefix}/lib/node_modules folder, instead of the current working directory.
  • bin files are linked to {prefix}/bin
  • man pages are linked to {prefix}/share/man

🫢 See Also 🫢

  • npm help "help config"

🫢 That’s the page, bestie. Source/version: NPM@12.2.1. Date: October 2026. Manual: NPM-SET(1). Mwah πŸ’‹
πŸ“¦ where this page comes from