Make all frontend dependencies explicit version numbers rather than minimums

[andrewtavis]

Terms

• I have searched open and closed feature requests
• I agree to follow activist's Code of Conduct

Description

The way that we've been doing frontend dependencies for the longest time is to have a minimum version number and let yarn figure out the rest. An issue with this is that it's making maintaining PRs for the frontend dramatically more difficult, as each time there's an added dependency we also get minor version updates that lead to overly complex merge conflicts with yarn.lock. With this in mind, it'd be great to have only explicit version numbers for the frontend in the pageage.json file.

We can set all current minimums as the explicit version number and work it out until we have a working build, and then from there we can update them regularly as needed :)

Note - related issues are:

• GitHub Actions dependency check #724
• Suppress warnings of "unmet peer dependencies" in frontend docker build #871

Contribution

Happy to support or work on this myself eventually! 😊

[andrewtavis]

CC @aasimsyed again :) Thanks for the chats on dependencies and for your work on that there yarn.lock! Let's try to have you not need to do that again :)

[andrewtavis]

One thing that's needed from here is also removing all of the packages that we don't need except to suppress the warnings :)

[tasawar-hussain]

I would like to take it up!

[andrewtavis]

Hey @tasawar-hussain 👋 Thanks for the interest! We talked yesterday that @aasimsyed was going to take this one, but I'll get you on the other two you wrote in :)

[andrewtavis]

@aasimsyed, can you write in here and I'll assign?