Maintenance/upgrade js dependencies #385
Merged
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.
References #382.
@justin808 here's the second PR for updating the dependencies. Note: This PR does NOT include the update of the react libraries. Apparently the new
react
,react-router
,react-dom
versions that were released added a lot of breaking changes. An example is removingPropTypes
from the react library and adding it to it's own npm module. I'm not sure the amount of updates this will cause, but I figured it was best to leave out of this PR for size.Any suggestions about how to tackle this?
This PR includes:
.nvmrc
engines
inpackage.json
'sAlso I noticed that npm was still included in the engines section of the
package.json
's. Any idea if this can be removed?Feel free to let me know any other suggestions you have!
This change is