Skip to content

NestJS v11 Support #17

Open
Open
@estiller

Description

@estiller

When updating NestJS to v11, we get a warning regarding unmet peer dependencies:

├─┬ nestjs-grpc-exceptions 0.2.2
│ ├── ✕ unmet peer @nestjs/common@"^9.0.0 || ^10.0.0": found 11.0.3
│ ├── ✕ unmet peer @nestjs/core@"^9.0.0 || ^10.0.0": found 11.0.3
│ └── ✕ unmet peer @nestjs/microservices@"^9.0.0 || ^10.0.0": found 11.0.3

I suspect there are no breaking changes that affect nestjs-grpc-exceptions and that the fix would be to update the allowed peer dependencies in the package.json file.

Should I open a PR for this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions