【问题】：volantis v5.7.4出现配置文件检查失败的错误 dev分支

[zehuajun]

检查清单

• 已经搜索过，没有发现类似 issue。
• 已经搜索过主题文档，没有发现相关内容。
• 已经尝试使用过最新版，问题依旧存在。

主题版本

5.7.4

复现地址

没有

问题描述

出现

配置文件检查失败！| Configuration check failed!

description 未配置！
请在站点配置 _config.yml 中配置 description
description主要用于SEO，告诉搜索引擎一个关于您站点的简单描述，通常建议在其中包含您网站的关键词。
see: https://hexo.io/zh-cn/docs/configuration
description is not configured!

/data/data/com.termux/files/home/hexo/themes/volantis/scripts/events/lib/check-environment.js:71
throw new Error('配置文件检查失败！| Configuration check failed!');
^

Error: 配置文件检查失败！| Configuration check failed!
at CheckConfError (/data/data/com.termux/files/home/hexo/themes/volantis/scripts/events/lib/check-environment.js:71:9)
at /data/data/com.termux/files/home/hexo/themes/volantis/scripts/events/lib/check-environment.js:38:17
at ChildProcess.exithandler (node:child_process:402:7)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5)

问题

主题安装操作

在themes目录中运行

git clone https://github.com/volantis-x/hexo-theme-volantis.git

mv hexo-theme-volantis volantis

cd ..

vim _config.yml

theme:volantis

然后运行hexo g就出现错误

配置文件

站点配置文件

在这里粘贴替换 `blog/_config.yml` 中修改过的部分

deploy:
type: git
repo: [email protected]:………………
branch: master

主题配置文件

在这里粘贴替换 `themes/volantis/_config.yml` 中修改过的部分

环境信息

node.js & npm

在这里粘贴替换 `node -v && npm -v` 输出的信息

v18.7.0
8.15.0

package.json

在这里粘贴替换 `npm ls --depth 0` 输出的信息

home@ /data/data/com.termux/files/home
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected]
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
├── [email protected] extraneous
└── [email protected] extraneous

[zehuajun]

在删除themes目录中的volantis文件夹后运行

cd ..
反回上级目录后

运行npm i hexo-theme-volantis命令后
运行hexo g
出现一样的错误

============================================================
配置文件检查失败！| Configuration check failed!

description 未配置！
请在站点配置 _config.yml 中配置 description
description主要用于SEO，告诉搜索引擎一个关于您站点的简单描述，通常建议在其中包含您网站的关键词。
see: https://hexo.io/zh-cn/docs/configuration
description is not configured!

/data/data/com.termux/files/home/hexo/node_modules/hexo-theme-volantis/scripts/events/lib/check-environment.js:71
throw new Error('配置文件检查失败！| Configuration check failed!');
^

Error: 配置文件检查失败！| Configuration check failed!
at CheckConfError (/data/data/com.termux/files/home/hexo/node_modules/hexo-theme-volantis/scripts/events/lib/check-environment.js:71:9)
at /data/data/com.termux/files/home/hexo/node_modules/hexo-theme-volantis/scripts/events/lib/check-environment.js:38:17
at ChildProcess.exithandler (node:child_process:402:7)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5)

Node.js v18.7.0

但目录不同

错误如图

Hexo

配置

您可以在 _config.yml 中修改大部分的配置。 网站 参数 描述 title 网站标题 subtitle 网站副标题 description 网站描述 keywords 网站的关键词。支持多个关键词。 author 您的名字 language 网站使用的语言。对于简体中文用户来说，使用不同的主题可能需要设置成不同的值，请参考你的主题的文档自行设置，常见的有

[zehuajun]

感谢，我已经解决了这个问题
Thank you. I have solved this problem

[so1ve]

有没有一种可能 报错是中文的

[Colsrch]

有没有一种可能 报错是中文的

[zehuajun]

报错就是中文
我还傻乎乎的在主题配置文件里找

[github-actions]

👋 Hello,
This issue has been marked as resolved. If there are other issues, please contact us with a new issue.

👋 您好，
此 issue 已经被标记为已解决，如果还有其它问题，请提出新的 issue 联系我们。