Upgrade dependent packages to latest version #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.yarn.lock
By upgrading yarn v1.10.1 (current stable),
yarn.lockhas added newintegritysection. So this PR has huge diff than usual inyarn.lock.Marpit
It includes the performance improvement of Marpit. Marp core is slower than plain Marpit because of many additional features, but it would still recieve a benefit of performance from Marpit v0.1.3.
When marp-team/marpit#79's benchmark has applied to Marp core, the result on Node v8 is below:
It becomes about 68% faster than previous version of core by updating Marpit.