diff options
| author | Alexey Ten <alexeyten@gmail.com> | 2021-09-07 15:55:03 +0300 |
|---|---|---|
| committer | Node.js GitHub Bot <github-bot@iojs.org> | 2021-09-07 22:59:15 +0300 |
| commit | 861c3e0fba0ddc41e436f923178174e648f2ffdb (patch) | |
| tree | 6be7fa99495249a08d911b9156816c2ca8e514c5 /doc/api | |
| parent | 5d34ef509e5da82bb0958e6621b9a1d5a952821a (diff) | |
doc: fix list indentation in corepack.md
PR-URL: https://github.com/nodejs/node/pull/40029
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Shingo Inoue <leko.noor@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Diffstat (limited to 'doc/api')
| -rw-r--r-- | doc/api/corepack.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/api/corepack.md b/doc/api/corepack.md index ac696062212..f5ee64e5158 100644 --- a/doc/api/corepack.md +++ b/doc/api/corepack.md @@ -73,10 +73,10 @@ The `prepare` command has [various flags][], consult the detailed The following binaries are provided through Corepack: -| Package manager | Binary names | -| --------------- | -------------- | +| Package manager | Binary names | +| --------------- | ----------------- | | [Yarn][] | `yarn`, `yarnpkg` | -| [pnpm][] | `pnpm`, `pnpx` | +| [pnpm][] | `pnpm`, `pnpx` | ## Common questions @@ -86,10 +86,10 @@ While Corepack could easily support npm like any other package manager, its shims aren't currently enabled by default. This has a few consequences: * It's always possible to run a `npm` command within a project configured to -be used with another package manager, since Corepack cannot intercept it. + be used with another package manager, since Corepack cannot intercept it. * While `npm` is a valid option in the [`"packageManager"`][] property, the -lack of shim will cause the global npm to be used. + lack of shim will cause the global npm to be used. ### Running `npm install -g yarn` doesn't work @@ -97,12 +97,12 @@ npm prevents accidentally overriding the Corepack binaries when doing a global install. To avoid this problem, consider one of the following options: * Don't run this command anymore; Corepack will provide the package manager -binaries anyway and will ensure that the requested versions are always -available, so installing the package managers explicitly isn't needed anymore. + 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 -override binaries, but you'll erase the Corepack ones in the process (should -that happen, run [`corepack enable`][] again to add them back). + override binaries, but you'll erase the Corepack ones in the process (should + that happen, run [`corepack enable`][] again to add them back). [Corepack]: https://github.com/nodejs/corepack [Corepack documentation]: https://github.com/nodejs/corepack#readme |