Migration guide
This article provides a set of guidelines for migrating from Nest version 7 to version 8. To learn more about the new features we've added in the v8, check out this link.
HTTP module#
The HttpModule exported from the @nestjs/common package has been deprecated and will be removed in the next major release.
Instead, please use the @nestjs/axios package (otherwise, there are no API differences).
gRPC strategy#
The original Node gRPC library (grpc) has been deprecated and will no longer receive feature updates.
With Nest v8, you should use the @grpc/grpc-js library instead.
NATS strategy#
NATS has released a new major version (2.0) which has many changes and it is not API compatible with nats@1.x.x.
If you interact with a Nest microservice (that uses NATS as a transfer layer), from a service written in a different framework, please, see their migration document to learn what's changed in v2.
Otherwise, you should not see any specific differences when communicating from one Nest microservice and another (although we use v2 now, there are no API differences - just make sure to upgrade the nats package: npm i nats@latest).
@All() decorator#
Routes annotated with the @All() decorator will now map to the router.all() method instead of the router.use().
Async listen/start methods#
listenAsync() and startAllMicroservicesAsync() methods have been deprecated.
Instead, simply use the listen() and startAllMicroservices() methods (they are async either way).
Socket.io#
The @nestjs/platform-socket.io package was upgraded to use the socket.io@4.x.x version (Nest v7 was based on the socket.io v2).
To learn more, check out these articles: Socket.io 3 Release and Socket.io 4 Release.
@nestjs/config package#
There was a minor breaking change in the registerAs function (typings), you can see what has changed in this PR.
@nestjs/graphql package#
There might be some small differences in how your auto-generated schema file may look like (changed types order). Also, if you use the schema-first approach, the automatically generated type definitions will change as there was a new Nullable<T> type introduced in the latest release.
Also, all HttpException errors thrown from your resolvers will be now automatically mapped to the corresponding ApolloError instances, unless you set the autoTransformHttpErrors configuration property (in the options object you pass into the GraphQLModule#forRoot() method) to false.
