codekingpro/portable-devtools

1---
2title: npm-bugs
3section: 1
4description: Report bugs for a package in a web browser
5---
6
7### Synopsis
8
9```bash
10npm bugs [<pkgname> [<pkgname> ...]]
11
12alias: issues
13```
14
15### Description
16
17This 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 tries to open it using the [`--browser` config](/using-npm/config#browser) param.
18If no package name is provided, it will search for a `package.json` in the current folder and use the `name` property.
19
20### Configuration
21
22#### `browser`
23
24* Default: macOS: `"open"`, Windows: `"start"`, Others: `"xdg-open"`
25* Type: null, Boolean, or String
26
27The browser that is called by npm commands to open websites.
28
29Set to `false` to suppress browser behavior and instead print urls to
30terminal.
31
32Set to `true` to use default system URL opener.
33
34
35
36#### `registry`
37
38* Default: "https://registry.npmjs.org/"
39* Type: URL
40
41The base URL of the npm registry.
42
43
44
45#### `workspace`
46
47* Default:
48* Type: String (can be set multiple times)
49
50Enable running a command in the context of the configured workspaces of the
51current project while filtering by running only the workspaces defined by
52this configuration option.
53
54Valid values for the `workspace` config are either:
55
56* Workspace names
57* Path to a workspace directory
58* Path to a parent workspace directory (will result in selecting all
59  workspaces within that folder)
60
61When set for the `npm init` command, this may be set to the folder of a
62workspace which does not yet exist, to create the folder and set it up as a
63brand new workspace within the project.
64
65This value is not exported to the environment for child processes.
66
67#### `workspaces`
68
69* Default: null
70* Type: null or Boolean
71
72Set to true to run the command in the context of **all** configured
73workspaces.
74
75Explicitly setting this to false will cause commands like `install` to
76ignore workspaces altogether. When not set explicitly:
77
78- Commands that operate on the `node_modules` tree (install, update, etc.)
79will link workspaces into the `node_modules` folder. - Commands that do
80other things (test, exec, publish, etc.) will operate on the root project,
81_unless_ one or more workspaces are specified in the `workspace` config.
82
83This value is not exported to the environment for child processes.
84
85#### `include-workspace-root`
86
87* Default: false
88* Type: Boolean
89
90Include the workspace root when workspaces are enabled for a command.
91
92When false, specifying individual workspaces via the `workspace` config, or
93all workspaces via the `workspaces` flag, will cause npm to operate only on
94the specified workspaces, and not on the root project.
95
96This value is not exported to the environment for child processes.
97
98### See Also
99
100* [npm docs](/commands/npm-docs)
101* [npm view](/commands/npm-view)
102* [npm publish](/commands/npm-publish)
103* [npm registry](/using-npm/registry)
104* [npm config](/commands/npm-config)
105* [npmrc](/configuring-npm/npmrc)
106* [package.json](/configuring-npm/package-json)
107