chore: fix 4 of 5 peer dependency warnings by updating dependencies #394
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 is a PR for PR #384.
It fixes 4 of the 5 npm warnings for npm install that tell you to install peer dependencies.
The remaining warning seems unsolvable right now, because we also need a newer version of webpack:
karma-webpack upgrades the webpack dependency in 4.0.0, but there's only a release candidate for that right now.
for tsify's dependency on browserify, i had to add browserify to the devDependencies. It's not ideal, because tsify might change that peer dependency in the future and then we can remove browserify as a dependency. But better than a warning, i think.
everything seems to work fine with this (npm install, karma tests, npm start, demo).