Fixed broken package.json, updated all deps and react example #115
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.
Vast majority of line changes come from package-lock.
Description of the change
This PR fixes some
package.json
discrepancies that were causingnpm install
to fail.The main discrepancy was in the versions declared for react (16.x) and react-dom (17.x). Once this was fixed, a few other deps needed adjustment.
In the end, they were all updated to their latest React 17-supporting versions.
React version on
peerDependencies
remains untouched, ranging from 16 to 18.The version of Typescript has also been bumped from 4 to 5. Although the source code is pure js.
eslint
andprettier
were also updated to their latest versions, these updates required that the rollup config js file be renamed to mjs due to its use of modules, and some minimal updates to the eslint config.The
.tools-versions
file which declared node 14 has been removed, the project should be able to be npm installed and built using any LTS node beginning in 14, something the ci checks already since the recent changes.Type of change
Checklists
Development
Code review