codekingpro/portable-devtools

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