Fixes #1534, Added Legacy Dependencies Check

[Metropass]

Issue This PR Addresses

Type of Change

Fixes #1534
and closed #1617 due to the branch being outdated

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

As of npm7.x, Peer Dependencies has had an overhaul, causing some of our dependencies not properly installing if a user runs npm install. This is a band-aid fix to use the legacy Peer Dependencies, until we fix the issue for forwards compatibility.

This is a final version of #1617, as this PR is rebased.

More Information on the Changes of Peer Dependencies can be found here

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[HyperTHD]

cc @chrispinkney

[chrispinkney]

Cool. From the (very minor) research I've done on this topic, it doesn't seem like this will cause doom and panic across our repo.

I guess this will be fine to remove in a few years when conflicting peer dependencies are a thing of the past? 🤷

[birtony]

LGTM! #1647 should help with updating our dependencies