[Includes security update] Upgrade dependent packages to latest #40
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.
Upgrade dependent packages to latest version by using
yarn upgrade-interactive --latest
. The motivation is as same as marp-team/marpit#96 and marp-team/marp-core#50.It includes an important upgrade of npm-run-all v4.1.5. The malicious code has been reported in v4.1.3's dependency. (
marp-cli
->marp-core
/marpit
->npm-run-all
->ps-tree
->event-stream
->[email protected]
[reported malicious code])By the reason as same as Upgrade dependent packages to latest #36,
rollup-plugin-pug
is not upgraded to the latest version. Node 6 maintenance LTS will end in April 2019, so we should keep the current verion until then it.marp-core is no longer using
markdown-it-katex
, so we are no more neededresolutions
field to prevent double-bundling.Currently we are working to the documentation at
docs
branch. We had planned that a next release will become to be the first minor release included documents and updates of package. However, we have to keep publishing pre-release versions because it is required the security measures like this PR.