chore: change dependencies version#5202
Merged
yoshinorin merged 2 commits intohexojs:v7.0.0from May 31, 2023
Merged
Conversation
Contributor
Author
|
The former one should be fixed in hexojs/hexo-front-matter#67, but since |
How to testgit clone -b dep-update https://github.com/Pcrab/hexo.git
cd hexo
npm install
npm test |
tomap
approved these changes
May 15, 2023
2 tasks
yoshinorin
approved these changes
May 31, 2023
Member
yoshinorin
left a comment
There was a problem hiding this comment.
@Pcrab
Thank you :)
We will release a new version of hexo-front-matter.
This was referenced Oct 23, 2023
This file contains hidden or 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.
What does it do?
npm and yarn
Since hexo-front-matter release v4.1.0, it uses typescript and requires exactly two parameters:
However, in hexo, it calls the
parsefunction mostly with only one parameter:Although in
package.jsonits version is defined as^4.0.0, npm and yarn will automatically install its latest version v4.1.0, which makes the build fail.pnpm
If we use
pnpm, it will usemoizev6.1.0, not its latest version v6.1.6, together withmicro-memoizv4.1.2.micro-memoizeused to contain itssrcfolder but was removed in v4.1.0.In
moizeits type definition contains:which no longer works with the latest
micro-memoiz. This is fixed in v6.1.6.Screenshots
with npm:
with pnpm:
Pull request tasks