feat(nest): update NestJS version to 7.0.0

[beeman]

This PR updates NestJS to the latest version. I've added the same versions that are used when creating a new app using the NestJS cli, including RxJS.

I've tested it in a playground and all seems to work as expected.

[FrozenPandaz]

@beeman

Thanks for the contribution!

Would you mind listing out any Breaking Changes in NestJS 7.0.0 and highlight any changes that were made? I see rxjs is now a peer dependency?

[beeman]

@FrozenPandaz thanks for reviewing!

(As far as I can tell...)

The only real breaking change in NestJS core is dropping support for Node v8.

Other than that, users of the packages @nestjs/microservices, @nestjs/graphql and @nestjs/terminus are advised to read the migration guide see what changed for them.

I've been using Nest v7 it since it's release in my Nx projects and I only needed to change how I used GraphQL.

Since Kamil did an awesome job keeping @nestjs/graphql backwards compatible, migration is trivial:

• Search/replace type-graphql with @nestjs/graphql
• Search/replace ResolveProperty with ResolveField.

After that we can get rid of the type-graphql dependency and the migration is done.

Let me know if you need anything else, or if you want me to list this somewhere specific.

The rxjs dependency is a peerDependency, so not essential to start a new NestJS api but recommended to install.

From looking at it though, we should probably also add reflect-metadata as a peerDependency to get rid of these:

warning " > @nestjs/core@7.0.9" has unmet peer dependency "reflect-metadata@^0.1.12".
warning " > @nestjs/common@7.0.9" has unmet peer dependency "reflect-metadata@^0.1.12".

[beeman]

@FrozenPandaz I pushed an updated version.

The PR now also updates the dependencies in the top-level package.json (this is what breaks CI?).

I also gave a shot at adding a migration script. Not sure if that's something that's desired, happy to remove again it if not :)

[FrozenPandaz]

Thank you for adding the migration file.

I think we should also provide migrations for the changes to imports.

Would you be able to give that a shot?

[beeman]

@FrozenPandaz for sure happy to take a look at that. Do you know of a similar migration that I could use as an example?

[FrozenPandaz]

Here is somewhere you can start? You may want to be more careful about which Symbols are brought over?

https://github.com/nrwl/nx/blob/master/packages/react/src/migrations/update-8-3-0/update-8-3-0.ts#L98

[beeman]

@FrozenPandaz that was a great pointer, I updated the migration to update the import from type-graphql to @nestjs/graphql, and remove the type-graphql dependency from package.json.

However, I have tried to rename the decorator (ResolveProperty -> ResolveField) but I could not get it working, my AST knowledge is not sufficient yet. Any pointers on how we can do that?

[juristr]

@beeman just adjusted a couple of things on top of ur PR. Thx again for all ur contributions 🙏 .

I also added a link to the NestJS migration docs, so ppl can check it out.

If the pipeline looks good I'll merge it tomorrow

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.