Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NestJS v11 Support #17

Open
estiller opened this issue Jan 20, 2025 · 0 comments
Open

NestJS v11 Support #17

estiller opened this issue Jan 20, 2025 · 0 comments

Comments

@estiller
Copy link

estiller commented Jan 20, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant