unmet peer graphql-subscriptions@^2.0.0: found 3.0.0

[kasir-barati]

Describe the bug
So it is not really a bug but can become one since graphql-subscriptions have changed their API since version 3.x.

https://github.com/apollographql/graphql-subscriptions/blob/master/CHANGELOG.md#300

asyncIterator is no longer available, instead asyncIterableIterator is the one that should be used.

Have you read the Contributing Guidelines?

Yep

To Reproduce
Steps to reproduce the behavior:

1. Create a new NestJS project

2.  pnpm add @ptc-org/nestjs-query-core @ptc-org/nestjs-query-graphql @ptc-org/nestjs-query-typeorm @nestjs/typeorm @nestjs/common @nestjs/graphql graphql graphql-subscriptions class-transformer class-validator dataloader typeorm

Then you can see this warning:

 WARN  Issues with peer dependencies found
.
└─┬ @ptc-org/nestjs-query-graphql 7.1.0
  └── ✕ unmet peer graphql-subscriptions@^2.0.0: found 3.0.0

Expected behavior
No warning

Screenshots

Desktop (please complete the following information):

• Node Version: 22.12.0
• Nestjs-query Version: 7.1.0

Additional context

I am currently working with this monorepo project inside a bigger repo: https://github.com/kasir-barati/nestjs-materials/tree/main/typeorm

[TriPSs]

Thanks, would you be willing to create a PR?

[kasir-barati]

Yeah sure. Why not. BTW thanks for this wonderful work. It is really good that this lib is still kicking.

[kasir-barati]

@TriPSs I am not familiar with the release plan, do yo think you can tell me how usually new releases are published on npm, if we have a doc for I'd love to take a look.

[TriPSs]

Useally I realse when there is something to release, now I did all the dependa bot things and went for food and forgot it 😅, let me release this.