update dependencies #332
Open
update dependencies #332
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this PR introduces updates to dependencies so that you can run
npm installwithout needing to resort to allowing legacy dependencies. This also updates the tooling to use Vite over react-scripts which is no longer maintained.These changes involve replacing several older libraries with newer counterparts, or with custom components that serve the same function. The goal was to make the transition as painless as possible, so for example the
riekpackage which offered inline elements has been replaced with components that do the same thing and look the same way, just not in a package that requires a lower version of react.Other packages like the react router, table display, and json editor were also replaced.