-
-
Notifications
You must be signed in to change notification settings - Fork 51
/
help__add.snap
186 lines (96 loc) · 4.46 KB
/
help__add.snap
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
---
source: tests/help.rs
expression: "sub_md(\"add\")"
---
stderr:
stdout:
# oro add
Adds one or more dependencies to the target package
### Usage:
```
oro add [OPTIONS] <SPECS>...
```
### Arguments
#### `<SPECS>...`
Specifiers for packages to add
### Options
#### `--prefix <PREFIX>`
Prefix to prepend to package versions for resolved NPM dependencies.
For example, if you do `oro add foo@1.2.3 --prefix ~`, this will write `"foo": "~1.2.3"` to your `package.json`.
\[default: ^]
#### `-D, --dev`
Add packages as devDependencies
#### `-O, --opt`
Add packages as optionalDependencies
\[aliases: optional]
#### `-h, --help`
Print help (see a summary with '-h')
#### `-V, --version`
Print version
### Apply Options
#### `--no-apply`
Prevent all apply operations from executing
#### `--prefer-copy`
When extracting packages, prefer to copy files files instead of linking them.
This option has no effect if hard linking fails (for example, if the cache is on a different drive), or if the project is on a filesystem that supports Copy-on-Write (zfs, btrfs, APFS (macOS), etc).
#### `--validate`
Validate the integrity of installed files.
When this is true, orogene will verify all files extracted from the cache, as well as verify that any files in the existing `node_modules` are unmodified. If verification fails, the packages will be reinstalled.
#### `--lockfile-only`
Whether to skip restoring packages into `node_modules` and just resolve the tree and write the lockfile
#### `--locked`
Make the resolver error if the newly-resolved tree would defer from an existing lockfile
\[aliases: frozen]
#### `--no-scripts`
Skip running install scripts
#### `--default-tag <DEFAULT_TAG>`
Default dist-tag to use when resolving package versions
\[default: latest]
#### `--concurrency <CONCURRENCY>`
Controls number of concurrent operations during various apply steps (resolution fetches, extractions, etc).
Tuning this might help reduce memory usage (if lowered), or improve performance (if increased).
\[default: 50]
#### `--script-concurrency <SCRIPT_CONCURRENCY>`
Controls number of concurrent script executions while running `run_script`.
This option is separate from `concurrency` because executing concurrent scripts is a much heavier operation.
\[default: 6]
#### `--no-lockfile`
Disable writing the lockfile after operations complete.
Note that lockfiles are only written after all operations complete successfully.
#### `--hoisted`
Use the hoisted installation mode, where all dependencies and their transitive dependencies are installed as high up in the `node_modules` tree as possible.
This can potentially mean that packages have access to dependencies they did not specify in their package.json, but it might be useful for compatibility.
By default, dependencies are installed in "isolated" mode, using a symlink/junction structure to simulate a dependency tree.
### Global Options
#### `--root <ROOT>`
Path to the project to operate on.
By default, Orogene will look up from the current working directory until it finds a directory with a `package.json` file or a `node_modules/` directory.
\[default: .]
#### `--registry <REGISTRY>`
Registry used for unscoped packages
\[default: https://registry.npmjs.org]
#### `--scoped-registry <SCOPED_REGISTRIES>`
Registry to use for a specific `@scope`, using `--scoped-registry @scope=https://foo.com` format.
Can be provided multiple times to specify multiple scoped registries.
#### `--credentials <CREDENTIALS>`
Credentials to apply to registries when they're accessed. You can provide credentials for multiple registries at a time, and different credential fields for a registry.
The syntax is `--credentials my.registry.com:username=foo --credentials my.registry.com:password=sekrit`.
#### `--cache <CACHE>`
Location of disk cache.
Default location varies by platform.
#### `--config <CONFIG>`
File to read configuration values from.
When specified, global configuration loading is disabled and configuration values will only be read from this location.
#### `--loglevel <LOGLEVEL>`
Log output level/directive.
Supports plain loglevels (off, error, warn, info, debug, trace) as well as more advanced directives in the format `target[span{field=value}]=level`.
\[default: info]
#### `-q, --quiet`
Disable all output
#### `--json`
Format output as JSON
#### `--no-progress`
Disable the progress bars
#### `--no-emoji`
Disable printing emoji.
By default, this will show emoji when outputting to a TTY that supports unicode.