FATAL YAMLException: Specified list of YAML types (or a single Type object) contains a non-Type object. occur in new node.js

[yzyyz1387]

For some reason, it seems that my blog environment has been destroyed, and the following error occurred when executing the hexo command. It may be caused by my mistake, can this problem be fixed? Thanks for your time :)

$ hexo clean
FATAL YAMLException: Specified list of YAML types (or a single Type object) contains a non-Type object.
    at D:\blog\[email protected]\node_modules\hexo\node_modules\js-yaml\lib\schema.js:104:13
    at Array.forEach (<anonymous>)
    at Schema.extend (D:\blog\[email protected]\node_modules\hexo\node_modules\js-yaml\lib\schema.js:102:12)
    at Object.<anonymous> (D:\blog\[email protected]\node_modules\hexo\lib\plugins\renderer\yaml.js:5:36)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at module.exports (D:\blog\[email protected]\node_modules\hexo\lib\plugins\renderer\index.js:15:16)
    at Hexo.init (D:\blog\[email protected]\node_modules\hexo\lib\hexo\index.js:235:35)
    at D:\blog\[email protected]\node_modules\hexo-cli\lib\hexo.js:49:17
    at tryCatcher (D:\blog\[email protected]\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (D:\blog\[email protected]\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (D:\blog\[email protected]\node_modules\bluebird\js\release\promise.js:604:18) {
  reason: 'Specified list of YAML types (or a single Type object) contains a non-Type object.',
  mark: undefined

version information：

$ npm -v
8.1.2
$ node -v
v16.13.2

[yoshinorin]

@yzyyz1387
Can you upgrade your hexo to 6.0.0?
4days ago, we faced a similar problem when testing hexo-generator-category. It was solved after upgrade hexo to 6.0.0

https://github.com/hexojs/hexo-generator-category/runs/5077429097?check_suite_focus=true

[yzyyz1387]

Thanks, this problem was solved after updating to 6.0.0, it may be caused by I updated node. But my hexo was version 5.4.1 before that, in which I made a lot of personalized configuration, after the update it caused no Compatible, is there any suggestions if I want to keep using the old version?

[yzyyz1387]

Looks like I'm doing too much wrong, I ran my backup on a virtual machine and it works, thanks again