Upgrade dependent packages to latest version #101
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.
This PR will upgrade dependent packages to latest version by using
yarn upgrade(-interactive) --latest
.About security
Have you heard about a recent malicious dependency? The update of
nodemon
in this PR is beating a deep dependency completely.npm has published a post about detail of the
event-stream
incident. Marpit and our packages managed by marp-team have already handled the incident in early (#96: last Sunday).Next action
To manage packages securely, we're going to run
yarn audit
when running CI or publishing to npm.