Mimi

See also https://github.com/hexojs/warehouse/issues/13

I'll close this issue, because the major performance overhead of Hexo is not reading or writing `db.json`, but processing the cross-refs, e.g. finding posts with a tag or tags of...

Added in https://github.com/hexojs/hexo/pull/5198

From the perspective of 2024, the support for multithreading in Node.js has not improved. The rendering process of posts heavily relies on Hexo's `ctx`, but without the ability to use...

I will close this Issue because my tests show that using ":name" achieves your expected result. If you find that ":name" is generating incorrect permanent links, please provide the blog...

@cqbzljt You can try to apply this patch: https://github.com/hexojs/hexo/pull/5118

I will close this Issue because I believe it has been fixed. If the problem still exists, please feel free to reopen it.

@jerryc127 恐怕这个问题无法被修复。例如，用户给出一个完全非法的 heading 顺序： h1, h3, h4, h2, h5, h1 你认为 Hexo 输出什么结果是合理的？

Regarding your initial requirement: > Of cause, it means that post will only be readable via source file, but I think that it's exactly what we need for private posts....

I will close this issue, as the Hexo maintenance team continues to have new members joining. Thank you all for your collective efforts and contributions to the open source community!