Open noraj opened 11 months ago
Did you put it under your-blog/source/_authors
or your-blog/themes/icarus/source/_authors
?
Under your-blog/source/_authors
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale bots...
Describe the bug
I have YAML files in
source/
, e.g.,source/_authors/noraj.yml
used for hexo-multiauthorBut when building (
hexo g
), I encounter those warnings:That becomes an error when serving (
hexo s
)System and Environment
_config.yml
N/A_config.icarus.yml
orthemes/icarus/_config.yml
N/A (default)_config.post.yml
, or_config.page.yml
) N/ATo Reproduce
cd
into empty folderhexo init
npm install -S hexo-theme-icarus hexo-renderer-inferno
hexo config theme icarus
cp _config.landscape.yml source/landscape.yml
hexo g && hexo s
Note: With this minimal reproduction steps, I have a different error:
Note2: Copying noraj.yml instead generates no error and YAML files are converted to JSON instead.
Expected behavior
YAML files would be ignored by
hexo-renderer-inferno
.Screenshots
N/A
Additional context
package.json
```json { "name": "hexo-site", "version": "0.0.0", "private": true, "hexo": { "version": "7.0.0" }, "dependencies": { "hexo": "7.0.0", "hexo-generator-archive": "2.0.0", "hexo-generator-category": "2.0.0", "hexo-generator-feed": "3.0.0", "hexo-generator-index": "3.0.0", "hexo-generator-json-content": "4.2.3", "hexo-generator-tag": "2.0.0", "hexo-i18n": "2.0.0", "hexo-multiauthor": "0.0.1", "hexo-pagination": "3.0.0", "hexo-renderer-ejs": "2.0.0", "hexo-renderer-inferno": "^0.1.3", "hexo-renderer-markdown-it": "7.1.0", "hexo-renderer-stylus": "3.0.0", "hexo-server": "3.0.0", "hexo-spoiler": "1.7.3", "hexo-tag-asciinema": "0.0.3", "hexo-tag-chart": "^1.0.8", "hexo-tag-embed": "^1.0.0", "hexo-theme-icarus": "^5.2.1" } } ```