NPM-BUGS(1)

💅 npm-bugs — report bugs for a package in a web browser, bestie

okay so this is the npm-bugs page from the npm manual set (that's the manual name right there, you're welcome 💖) and honestly? it's a little cutie. let's get into it.

---

✨ NAME ✨

npm-bugs — Report bugs for a package in a web browser 🐛🦋

🌸 Synopsis 🌸

npm bugs [<pkgname> [<pkgname> ...]]

alias: issues

no cap, you can throw it more than one package name. slay.

---

🎀 DESCRIPTION 🎀

so here's the vibe: this command tries to guess at the likely location of a package's bug tracker URL, or the mailto URL of the support email 👀 — and then it tries to open that thing using the --browser config param (that's the config page at /using-npm/config#browser, iykyk).

and if you don't give it a package name at all? no worries bestie, it goes looking for a package.json in the current folder and uses the name property from there. lowkey smart ngl.

---

⚙️ CONFIGURATION ⚙️

🖥️ browser

• Default: macOS: "open", Windows: "start", Others: "xdg-open"
• Type: null, Boolean, or String

this is the browser that npm commands call to open websites 🌐.

set it to false to suppress browser behavior and instead print urls to terminal (very demure, very mindful, terminal-only queen 👑).

set it to true to use the default system URL opener.

📦 registry

• Default: "https://registry.npmjs.org/"
• Type: URL

the base URL of the npm registry. that's it, that's the whole thing 💅

🗂️ workspace

• Default: (empty)
• Type: String (can be set multiple times)

enable running a command in the context of the configured workspaces of the current project, while filtering by running only the workspaces defined by this configuration option 🔥

valid values for the workspace config are either:

• Workspace names
• Path to a workspace directory
• Path to a parent workspace directory (will result in selecting all workspaces within that folder)

when set for the npm init command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project 🌱 iconic.

this value is not exported to the environment for child processes. periodt.

🧚 workspaces

• Default: null
• Type: null or Boolean

set to true to run the command in the context of all configured workspaces 🫶

explicitly setting this to false will cause commands like install to ignore workspaces altogether. and when it's not set explicitly:

• Commands that operate on the node_modules tree (install, update, etc.) will link workspaces into the node_modules folder.
• Commands that do other things (test, exec, publish, etc.) will operate on the root project, unless one or more workspaces are specified in the workspace config.

this value is not exported to the environment for child processes either. same rule, fr fr.

🌈 include-workspace-root

• Default: false
• Type: Boolean

include the workspace root when workspaces are enabled for a command ⭐

when false, specifying individual workspaces via the workspace config, or all workspaces via the workspaces flag, will cause npm to operate only on the specified workspaces, and not on the root project. no crumbs left for the root 💀

and yep — this value is not exported to the environment for child processes. three for three 🎯

---

👀 SEE ALSO 👀

• npm help docs
• npm help view
• npm help publish
• npm help registry
• npm help config
• npm help npmrc
• package.json at /configuring-npm/package-json 🦋

---

aaaaand that's the whole page, bestie 🎀 go forth and file those bugs responsibly ✨

sign-off moment: this was NPM@12.2.1, dated October 2026 — love her, gotta cite her 💜🙈