Upgrade dependent packages to the latest version #125
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
yhatt
changed the title
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.
This PR will upgrade dependent packages to the latest version by using
yarn upgrade --latest(but excepted Puppeteer).Notable changes
pkgis re-upgraded to v4.4. We have already known in #112 that the automated standalone build for Windows with pkg 4.4 raises segfault error, but pkg 4.3 cannot work the updatedfast-globv3 (deep dependency ofglobbyv10) caused by the difference of Node version.Only a way left is making standalone build in Windows environment with pkg 4.4. We already have Azure Pipelines to run CI in Windows, so we can build standalone binary in Azure Pipelines (Release pipeline) automatically.