Update dependencies - Githubissues

ryhinchey commented 3 years ago

This PR:

updates all possible dependencies.
fixes linting issues that either existed on main or were introduced when dependencies were updated
applies prettier to all files

Description

In an effort to modernize the code base (and build up to a context/hooks refactor with newer version of React), this PR gets most dependencies up to date and fixes linting issues that were either existing or introduced due to the upgrade of various linting dependencies.

Motivation and Context

This is a first step to get all dependencies up to date and introduce newer React APIs

How Has This Been Tested?

All tests and linting passes
build passes
webpack dev server works as expected

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (adding or updating documentation)
[x] Dependency update

Checklist:

[ ] My change requires a change to the documentation and I have updated the documentation accordingly.
[x] My changes are in sync with the code style of this project.
[x] There aren't any other open Pull Requests for the same issue/update.
[ ] These changes should be applied to a maintenance branch.
[ ] This change requires cross browser checks.
[ ] This change adds additional environment variable requirements for react-albus users.
[x] I have added the Apache 2.0 license header to any new files created.

JamesSingleton commented 3 years ago

@ryhinchey, the first commit should include BREAKING CHANGE as it looks like we are dropping support for some versions of Node along with other dep updates.

ryhinchey commented 3 years ago

@JamesSingleton does it need to be the first? My commit about dropping node support added a Breaking Change description and an apostrophe after the scope