Skip to content

Commit f39298f

Browse files
authored
docs(migration): Adding a section for upgrading packages
Adding a new section to the Migration guide letting users know there is no `update` command and to use ncu per Member recommendation.
1 parent d6c53d2 commit f39298f

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

content/migration.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@ This article provides a set of guidelines for migrating from Nest version 9 to v
44
To learn more about the new features we've added in v10, check out this (_ARTICLE AVAILABLE SOON_).
55
There were some very minor breaking changes that shouldn't affect most users - you can find the full list of them [here](https://github.com/nestjs/nest/releases/tag/v10.0.0).
66

7+
### Upgrading Packages
8+
9+
The Nest CLI does not include an `update` command. While you can upgrade your packages manually, we recommend using [ncu (npm check updates)](https://npmjs.com/package/npm-check-updates).
10+
711
### Cache module
812

913
The `CacheModule` has been removed from the `@nestjs/common` package and is now available as a standalone package - `@nestjs/cache-manager`. This change was made to avoid unnecessary dependencies in the `@nestjs/common` package. You can learn more about the `@nestjs/cache-manager` package [here](https://docs.nestjs.com/techniques/caching).

0 commit comments

Comments
 (0)