graphql peer dependencies mismatch

[marvinroger]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

The graphql dependency does not match the peer dependencies requirements.

Steps to reproduce

Installing with yarn prints peer dependencies issues.

Actual Outcome

➤ YN0000: parse-server@npm:5.2.0 provides graphql@npm:15.7.1 with version 15.7.1, which doesn't satisfy the following requirements:

➤ YN0000: subscriptions-transport-ws@npm:0.11.0 [b75e4] → ^15.7.2 || ^16.0.0 ✘

Expected Outcome

Environment

No warning.

Server

• Parse Server version: 5.2.0

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

I suppose even with the PR, we will continue to run into these mismatches in the future. What can we do about that?

[marvinroger]

The only way I've found is to use Yarn Berry, which prints warnings when there's such a mismatch.
AFAIK, npm does not provide these kind of hints, but maybe a CI check like https://github.com/christopherthielen/check-peer-dependencies can do the trick?