-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hexo build failed due to type issue #5326
hexo build failed due to type issue #5326
Comments
It's time to release a new version of hexo-front-matter |
Ready for release hexo-front-matter v4.2.0. |
still exists another I think it need time to investigate and update. we could postpone this issue and release v7 first. |
maybe we can fix it in #5271 ? |
https://github.com/hexojs/hexo-fs/blob/72f16b383bce2a438aed3076e47be352f9e41d1c/lib/fs.ts#L236-L237 The file encoding defaults to utf-8, so the type is basically string |
https://nodejs.org/docs/latest-v18.x/api/fs.html#fspromisesreadfilepath-options
|
yes |
Besides, I found that
However, The signature of the writeFile function is
null is allowed to be passed in |
thanks! test passed. |
Originally posted by @Pcrab in #5202 (comment)in #5202, we lock hexo-front-matter version to 4.0.0
hexo/package.json
Line 47 in 2a2cc9a
hexo build failed
after hexojs/hexo-front-matter#67, hexo still have another types issue, which leads build failed.
The text was updated successfully, but these errors were encountered: