Commit 846e7e8
doc: fix list indentation in corepack.md
PR-URL: #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>1 parent 105c9e6 commit 846e7e8
1 file changed
Lines changed: 9 additions & 9 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -73,10 +73,10 @@ The `prepare` command has [various flags][], consult the detailed | |||
| 73 | 73 | ||
| 74 | 74 | The following binaries are provided through Corepack: | |
| 75 | 75 | ||
| 76 | - | Package manager | Binary names | | ||
| 77 | - | --------------- | -------------- | | ||
| 76 | + | Package manager | Binary names | | ||
| 77 | + | --------------- | ----------------- | | ||
| 78 | 78 | | [Yarn][] | `yarn`, `yarnpkg` | | |
| 79 | - | [pnpm][] | `pnpm`, `pnpx` | | ||
| 79 | + | [pnpm][] | `pnpm`, `pnpx` | | ||
| 80 | 80 | ||
| 81 | 81 | ## Common questions | |
| 82 | 82 | ||
@@ -86,23 +86,23 @@ While Corepack could easily support npm like any other package manager, its | |||
| 86 | 86 | shims aren't currently enabled by default. This has a few consequences: | |
| 87 | 87 | ||
| 88 | 88 | * It's always possible to run a `npm` command within a project configured to | |
| 89 | - be used with another package manager, since Corepack cannot intercept it. | ||
| 89 | + be used with another package manager, since Corepack cannot intercept it. | ||
| 90 | 90 | ||
| 91 | 91 | * While `npm` is a valid option in the [`"packageManager"`][] property, the | |
| 92 | - lack of shim will cause the global npm to be used. | ||
| 92 | + lack of shim will cause the global npm to be used. | ||
| 93 | 93 | ||
| 94 | 94 | ### Running `npm install -g yarn` doesn't work | |
| 95 | 95 | ||
| 96 | 96 | npm prevents accidentally overriding the Corepack binaries when doing a global | |
| 97 | 97 | install. To avoid this problem, consider one of the following options: | |
| 98 | 98 | ||
| 99 | 99 | * Don't run this command anymore; Corepack will provide the package manager | |
| 100 | - binaries anyway and will ensure that the requested versions are always | ||
| 101 | - available, so installing the package managers explicitly isn't needed anymore. | ||
| 100 | + binaries anyway and will ensure that the requested versions are always | ||
| 101 | + available, so installing the package managers explicitly isn't needed anymore. | ||
| 102 | 102 | ||
| 103 | 103 | * Add the `--force` to `npm install`; this will tell npm that it's fine to | |
| 104 | - override binaries, but you'll erase the Corepack ones in the process (should | ||
| 105 | - that happen, run [`corepack enable`][] again to add them back). | ||
| 104 | + override binaries, but you'll erase the Corepack ones in the process (should | ||
| 105 | + that happen, run [`corepack enable`][] again to add them back). | ||
| 106 | 106 | ||
| 107 | 107 | [Corepack]: https://github.com/nodejs/corepack | |
| 108 | 108 | [Corepack documentation]: https://github.com/nodejs/corepack#readme | |
0 commit comments