Upgrade Node LTS and dependent packages to the latest version #243
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
|
Now lodash vulnerability has been fixed in the latest release! I ran |
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.
Upgraded Node LTS and dependent packages to the latest version via
yarn upgrade --latest.Important
As same as marp-team/marp-vscode#151, we still cannot bump due to failed audit check: https://www.npmjs.com/advisories/1523Track the status for the new release oflodashat https://github.com/lodash/lodash/issues/4837.Notable changes
lodashin deep dependency.puppeteer-core) has bumped to v5 as early from Upgrade Node LTS and dependent packages to the latest version #237. It includes some removals of deprecated features.chrome-launchermakes faster to resolve the path of Google Chrome in macOS.