diff options
| author | Steven <steven@ceriously.com> | 2021-11-09 02:28:28 +0300 |
|---|---|---|
| committer | Richard Lau <rlau@redhat.com> | 2022-01-25 21:20:15 +0300 |
| commit | 4477da858fab9f3bb21236832cbc553303a8d3a5 (patch) | |
| tree | 01c170d1d1c80a2fcf0fce86f5b568ffdad1c5fa | |
| parent | 004eafbebf31945be0ec9c13432c503cfacb21db (diff) | |
doc: fix corepack grammar for `--force` flag
PR-URL: https://github.com/nodejs/node/pull/40762
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
Reviewed-By: Voltrex <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| -rw-r--r-- | doc/api/corepack.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/api/corepack.md b/doc/api/corepack.md index 1e30256b491..3277e9cefbf 100644 --- a/doc/api/corepack.md +++ b/doc/api/corepack.md @@ -100,7 +100,7 @@ install. To avoid this problem, consider one of the following options: binaries anyway and will ensure that the requested versions are always available, so installing the package managers explicitly isn't needed anymore. -* Add the `--force` to `npm install`; this will tell npm that it's fine to +* Add the `--force` flag to `npm install`; this will tell npm that it's fine to override binaries, but you'll erase the Corepack ones in the process (should that happen, run [`corepack enable`][] again to add them back). |