hexo g执行时报错TypeError: Cannot read properties of undefined (reading 'plugins')

[mountainmist1]

Node.js and NPM Information

v16.20.2
8.19.4

Package dependencies Information

[email protected] /root/blog
├── @next-theme/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

在这之前都可以正常部署，不知道是动了什么文件或是什么问题

[stevenjoezhang]

可能是主题配置里面的vendors选项被弄坏了。默认的是这样的：

hexo-theme-next/_config.yml

Lines 908 to 921 in 77adbf5

	vendors:
	# The CDN provider of NexT internal scripts.
	# Available values: local | jsdelivr | unpkg | cdnjs | custom
	# Warning: If you are using the latest master branch of NexT, please set `internal: local`
	internal: local
	# The default CDN provider of third-party plugins.
	# Available values: local | jsdelivr | unpkg | cdnjs | custom
	# Dependencies for `plugins: local`: https://github.com/next-theme/plugins
	plugins: cdnjs
	# Custom CDN URL
	# For example:
	# custom_cdn_url: https://cdn.jsdelivr.net/npm/${npm_name}@${version}/${minified}
	# custom_cdn_url: https://cdnjs.cloudflare.com/ajax/libs/${cdnjs_name}/${version}/${cdnjs_file}
	custom_cdn_url:

你可以检查一下你本地的版本是不是改过

[stevenjoezhang]

看着也没问题，你重新安装依赖试试

rm -rf package-lock.json node_modules
npm i
npx hexo cl
npx hexo g

[mountainmist1]

# npm i
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@firebase/[email protected]',
npm WARN EBADENGINE   required: { node: '>=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18.17' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated @types/[email protected]: This is a stub types definition. dompurify provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Use your platform's native DOMException instead
npm WARN deprecated [email protected]: Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead.
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 612 packages in 33s

98 packages are looking for funding
  run `npm fund` for details

之前也尝试重新删除安装过，不知道上面的安装报错是否有影响，重新安装后还是报同样的错

# npx hexo cl && npx hexo g
INFO  Validating config
INFO  Deleted database.
INFO  Validating config
INFO  ==================================
  ███╗   ██╗███████╗██╗  ██╗████████╗
  ████╗  ██║██╔════╝╚██╗██╔╝╚══██╔══╝
  ██╔██╗ ██║█████╗   ╚███╔╝    ██║
  ██║╚██╗██║██╔══╝   ██╔██╗    ██║
  ██║ ╚████║███████╗██╔╝ ██╗   ██║
  ╚═╝  ╚═══╝╚══════╝╚═╝  ╚═╝   ╚═╝
========================================
NexT version 8.20.0
Documentation: https://theme-next.js.org
========================================
INFO  Start processing
WARN  The following packages are not found by `@next-theme/plugins`.
WARN  ENOENT: no such file or directory, stat '/root/blog/node_modules//darkmode-js'
WARN  ENOENT: no such file or directory, stat '/root/blog/node_modules//valine'
WARN  Maybe you can find the solution here: https://github.com/next-theme/plugins#debug
FATAL Something's wrong. Maybe you can find the solution here: https://hexo.io/docs/troubleshooting.html
TypeError: Cannot read properties of undefined (reading 'plugins')
    at module.exports (/root/blog/themes/next/scripts/events/lib/vendors.js:22:9)
    at Hexo.<anonymous> (/root/blog/themes/next/scripts/events/index.js:9:27)
    at Hexo.tryCatcher (/root/blog/node_modules/bluebird/js/release/util.js:16:23)
    at Hexo.<anonymous> (/root/blog/node_modules/bluebird/js/release/method.js:15:34)
    at /root/blog/node_modules/hexo/dist/extend/filter.js:58:67
    at tryCatcher (/root/blog/node_modules/bluebird/js/release/util.js:16:23)
    at Object.gotValue (/root/blog/node_modules/bluebird/js/release/reduce.js:166:18)
    at Object.gotAccum (/root/blog/node_modules/bluebird/js/release/reduce.js:155:25)
    at Object.tryCatcher (/root/blog/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/root/blog/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/root/blog/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromiseCtx (/root/blog/node_modules/bluebird/js/release/promise.js:641:10)
    at _drainQueueStep (/root/blog/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/root/blog/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/root/blog/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/root/blog/node_modules/bluebird/js/release/async.js:15:14)

[stevenjoezhang]

很奇怪，我也想不出来是什么问题。你方便把/root/blog目录下的完整代码传到GitHub上面，或者打包发给我嘛？（可以先把一些个人敏感信息删掉）我本地调试一下看看能不能复现。

[mountainmist1]

当我准备把blog文件备份到另外目录并删除一些无用的文件打包发你时，我再次执行了npx hexo cl && npx hexo g，这次它没有报错了。
我发现是_config.yml_20241219这个备份文件的问题，当我删除它之后，执行hexo g 就没有报错了。

当我重新将/root/blog/themes/next中的_config_yaml备份之后，报错就重新出现了

cp _config.yml _config.yml_bak

[stevenjoezhang]

问题解决了就好～

[mountainmist1]

感谢大佬

[haibara-jian]

重复了该问题，也是把备份配置文件放在其他目录就可以了

[stevenjoezhang]

Hexo这边应该已经修复了： hexojs/hexo#5591 可以更新看看