Skip to content

Commit f3c02ff

Browse files
SchnizSchniz
committed
update command docs
1 parent 68a6793 commit f3c02ff

File tree

1 file changed

+92
-27
lines changed

1 file changed

+92
-27
lines changed

‎docs/commands.md

+92-27
Original file line numberDiff line numberDiff line change
@@ -59,12 +59,17 @@ Options:
5959
6060
[env: FNM_COREPACK_ENABLED]
6161
62-
--resolve-engines
62+
--resolve-engines [<RESOLVE_ENGINES>]
6363
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
64-
Experimental: This feature is subject to change.
64+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
65+
6566
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
67+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
68+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
69+
do that.
6670
6771
[env: FNM_RESOLVE_ENGINES]
72+
[possible values: true, false]
6873
6974
-h, --help
7075
Print help (see a summary with '-h')
@@ -137,12 +142,17 @@ Options:
137142
138143
[env: FNM_COREPACK_ENABLED]
139144
140-
--resolve-engines
145+
--resolve-engines [<RESOLVE_ENGINES>]
141146
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
142-
Experimental: This feature is subject to change.
147+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
148+
143149
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
150+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
151+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
152+
do that.
144153
145154
[env: FNM_RESOLVE_ENGINES]
155+
[possible values: true, false]
146156
147157
-h, --help
148158
Print help (see a summary with '-h')
@@ -194,12 +204,17 @@ Options:
194204
195205
[env: FNM_COREPACK_ENABLED]
196206
197-
--resolve-engines
207+
--resolve-engines [<RESOLVE_ENGINES>]
198208
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
199-
Experimental: This feature is subject to change.
209+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
210+
200211
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
212+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
213+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
214+
do that.
201215
202216
[env: FNM_RESOLVE_ENGINES]
217+
[possible values: true, false]
203218
204219
-h, --help
205220
Print help (see a summary with '-h')
@@ -267,12 +282,17 @@ Options:
267282
268283
[env: FNM_COREPACK_ENABLED]
269284
270-
--resolve-engines
285+
--resolve-engines [<RESOLVE_ENGINES>]
271286
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
272-
Experimental: This feature is subject to change.
287+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
288+
273289
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
290+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
291+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
292+
do that.
274293
275294
[env: FNM_RESOLVE_ENGINES]
295+
[possible values: true, false]
276296
277297
-h, --help
278298
Print help (see a summary with '-h')
@@ -334,12 +354,17 @@ Options:
334354
335355
[env: FNM_COREPACK_ENABLED]
336356
337-
--resolve-engines
357+
--resolve-engines [<RESOLVE_ENGINES>]
338358
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
339-
Experimental: This feature is subject to change.
359+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
360+
340361
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
362+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
363+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
364+
do that.
341365
342366
[env: FNM_RESOLVE_ENGINES]
367+
[possible values: true, false]
343368
344369
-h, --help
345370
Print help (see a summary with '-h')
@@ -406,12 +431,17 @@ Options:
406431
407432
[env: FNM_COREPACK_ENABLED]
408433
409-
--resolve-engines
434+
--resolve-engines [<RESOLVE_ENGINES>]
410435
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
411-
Experimental: This feature is subject to change.
436+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
437+
412438
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
439+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
440+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
441+
do that.
413442
414443
[env: FNM_RESOLVE_ENGINES]
444+
[possible values: true, false]
415445
416446
-h, --help
417447
Print help (see a summary with '-h')
@@ -468,12 +498,17 @@ Options:
468498
469499
[env: FNM_COREPACK_ENABLED]
470500
471-
--resolve-engines
501+
--resolve-engines [<RESOLVE_ENGINES>]
472502
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
473-
Experimental: This feature is subject to change.
503+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
504+
474505
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
506+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
507+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
508+
do that.
475509
476510
[env: FNM_RESOLVE_ENGINES]
511+
[possible values: true, false]
477512
478513
-h, --help
479514
Print help (see a summary with '-h')
@@ -532,12 +567,17 @@ Options:
532567
533568
[env: FNM_COREPACK_ENABLED]
534569
535-
--resolve-engines
570+
--resolve-engines [<RESOLVE_ENGINES>]
536571
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
537-
Experimental: This feature is subject to change.
572+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
573+
538574
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
575+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
576+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
577+
do that.
539578
540579
[env: FNM_RESOLVE_ENGINES]
580+
[possible values: true, false]
541581
542582
-h, --help
543583
Print help (see a summary with '-h')
@@ -593,12 +633,17 @@ Options:
593633
594634
[env: FNM_COREPACK_ENABLED]
595635
596-
--resolve-engines
636+
--resolve-engines [<RESOLVE_ENGINES>]
597637
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
598-
Experimental: This feature is subject to change.
638+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
639+
599640
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
641+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
642+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
643+
do that.
600644
601645
[env: FNM_RESOLVE_ENGINES]
646+
[possible values: true, false]
602647
603648
-h, --help
604649
Print help (see a summary with '-h')
@@ -656,12 +701,17 @@ Options:
656701
657702
[env: FNM_COREPACK_ENABLED]
658703
659-
--resolve-engines
704+
--resolve-engines [<RESOLVE_ENGINES>]
660705
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
661-
Experimental: This feature is subject to change.
706+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
707+
662708
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
709+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
710+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
711+
do that.
663712
664713
[env: FNM_RESOLVE_ENGINES]
714+
[possible values: true, false]
665715
666716
-h, --help
667717
Print help (see a summary with '-h')
@@ -713,12 +763,17 @@ Options:
713763
714764
[env: FNM_COREPACK_ENABLED]
715765
716-
--resolve-engines
766+
--resolve-engines [<RESOLVE_ENGINES>]
717767
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
718-
Experimental: This feature is subject to change.
768+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
769+
719770
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
771+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
772+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
773+
do that.
720774
721775
[env: FNM_RESOLVE_ENGINES]
776+
[possible values: true, false]
722777
723778
-h, --help
724779
Print help (see a summary with '-h')
@@ -782,12 +837,17 @@ Options:
782837
783838
[env: FNM_COREPACK_ENABLED]
784839
785-
--resolve-engines
840+
--resolve-engines [<RESOLVE_ENGINES>]
786841
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
787-
Experimental: This feature is subject to change.
842+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
843+
788844
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
845+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
846+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
847+
do that.
789848
790849
[env: FNM_RESOLVE_ENGINES]
850+
[possible values: true, false]
791851
792852
-h, --help
793853
Print help (see a summary with '-h')
@@ -798,7 +858,7 @@ Options:
798858
```
799859
Uninstall a Node.js version
800860
801-
> Warning: when providing an alias, it will remove the Node version the alias is pointing to, along with the other aliases that point to the same version.
861+
> Warning: when providing an alias, it will remove the Node version the alias > is pointing to, along with the other aliases that point to the same version.
802862
803863
Usage: fnm uninstall [OPTIONS] [VERSION]
804864
@@ -845,12 +905,17 @@ Options:
845905
846906
[env: FNM_COREPACK_ENABLED]
847907
848-
--resolve-engines
908+
--resolve-engines [<RESOLVE_ENGINES>]
849909
Resolve `engines.node` field in `package.json` whenever a `.node-version` or `.nvmrc` file is not present.
850-
Experimental: This feature is subject to change.
910+
This feature is enabled by default. To disable it, provide `--resolve-engines=false`.
911+
851912
Note: `engines.node` can be any semver range, with the latest satisfying version being resolved.
913+
Note 2: If you disable it, please open an issue on GitHub describing _why_ you disabled it.
914+
In the future, disabling it might be a no-op, so it's worth knowing any reason to
915+
do that.
852916
853917
[env: FNM_RESOLVE_ENGINES]
918+
[possible values: true, false]
854919
855920
-h, --help
856921
Print help (see a summary with '-h')

0 commit comments

Comments
 (0)