diff options
| -rw-r--r-- | docs/cli/update.md | 2 | ||||
| -rw-r--r-- | docs/install/overrides.md | 4 |
2 files changed, 2 insertions, 4 deletions
diff --git a/docs/cli/update.md b/docs/cli/update.md index 8ebfd6119..dfda37f01 100644 --- a/docs/cli/update.md +++ b/docs/cli/update.md @@ -1,5 +1,3 @@ -## `bun update` - To update all dependencies to the latest version _that's compatible with the version range specified in your `package.json`_: ```sh diff --git a/docs/install/overrides.md b/docs/install/overrides.md index 60d9e2172..27f5a92b2 100644 --- a/docs/install/overrides.md +++ b/docs/install/overrides.md @@ -34,7 +34,7 @@ node_modules But what if a security vulnerability was introduced in `bar@4.5.6`? We may want a way to pin `bar` to an older version that doesn't have the vulerability. This is where `"overrides"`/`"resolutions"` come in. -### `"overrides"` +## `"overrides"` Add `bar` to the `"overrides"` field in `package.json`. Bun will defer to the specified version range when determining which version of `bar` to install, whether it's a dependency or a metadependency. @@ -54,7 +54,7 @@ Add `bar` to the `"overrides"` field in `package.json`. Bun will defer to the sp } ``` -### `"resolutions"` +## `"resolutions"` The syntax is similar for `"resolutions"`, which is Yarn's alternative to `"overrides"`. Bun supports this feature to make migration from Yarn easier. |