啰里啰嗦

好像好久没有更新博客了，今年疫情很多人都过的不是很好，又到年底了，提前祝大家新年快乐吧😂，希望各位读者能够在新的一年蒸蒸日上，早日摆脱不开心，心想事成。😁哈哈~

问题

1丶hexo命令操作时出现的问题

hexo -v出现的问题

$ hexo -v
(node:9876) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:9876) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:9876) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
(node:9876) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(node:9876) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:9876) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
hexo: 4.2.0
hexo-cli: 3.1.0
os: Windows_NT 10.0.18363 win32 x64
node: 14.0.0
v8: 8.1.307.30-node.30
uv: 1.37.0
zlib: 1.2.11
brotli: 1.0.7
ares: 1.16.0
modules: 83
nghttp2: 1.40.0
napi: 6
llhttp: 2.0.4
openssl: 1.1.1f
cldr: 36.1
icu: 66.1
tz: 2019c
unicode: 13.0

hexo d 和 hexo g 出现的问题

$ hexo d -g
(node:3908) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:3908) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:3908) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
(node:3908) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(node:3908) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:3908) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
INFO  Start processing
INFO  Files loaded in 94 ms
INFO  0 files generated in 22 ms
INFO  Deploying: git
INFO  Clearing .deploy_git folder...
INFO  Copying files from public folder...
FATAL Something's wrong. Maybe you can find the solution here: https://hexo.io/docs/troubleshooting.html
TypeError [ERR_INVALID_ARG_TYPE]: The "mode" argument must be integer. Received an instance of Object
    at copyFile (fs.js:1890:10)
    at tryCatcher (D:\Blog\node_modules\bluebird\js\release\util.js:16:23)
    at ret (eval at makeNodePromisifiedEval (D:\Node\node_global\node_modules\hexo-cli\node_modules\bluebird\js\release\promisify.js:184:12), <anonymous>:13:39)
    at D:\Blog\node_modules\hexo-fs\lib\fs.js:144:39
    at tryCatcher (D:\Blog\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (D:\Blog\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (D:\Blog\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (D:\Blog\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (D:\Blog\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (D:\Blog\node_modules\bluebird\js\release\promise.js:673:18)
    at Promise._resolveCallback (D:\Blog\node_modules\bluebird\js\release\promise.js:466:57)
    at Promise._settlePromiseFromHandler (D:\Blog\node_modules\bluebird\js\release\promise.js:559:17)
    at Promise._settlePromise (D:\Blog\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (D:\Blog\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (D:\Blog\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (D:\Blog\node_modules\bluebird\js\release\promise.js:673:18)
    at Promise._resolveCallback (D:\Blog\node_modules\bluebird\js\release\promise.js:466:57)
    at Promise._settlePromiseFromHandler (D:\Blog\node_modules\bluebird\js\release\promise.js:559:17)
    at Promise._settlePromise (D:\Blog\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (D:\Blog\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (D:\Blog\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (D:\Blog\node_modules\bluebird\js\release\promise.js:673:18)

解决

出现以上的这些问题，博主大胆猜测是因为node版本太高导致的，切换成低版本的node来安装和编译Hexo就可以了。

为什么是猜测呢，因为博主原先是安装了最新版node14.15.1.0，然后卸载重新安装了一个之前存在U盘里的node12.5.0.0版本，这个问题就解决了。😂知道具体原因的朋友也可以在现房评论区告诉博主，么么哒~

2丶MarkdownPad发生HTML渲染组件出错的

此前是WIN7得到电脑，写这篇博文的时候博主换成了WIN10系统的电脑，然后MarkdowPad就发生了错误，提示如图:

MarkdowPad错误

解决方法

出现问题当然第一时间是请教万能的网友了，于是博主就百度了一下相关的关键词，果然发现有网友也出现过这个问题，于是博主不要脸的作为本博文的一节借鉴（抄？）了过来，也算是给自己做了一个小小的笔记吧。🤣

反正就是win8跟win10都会发生，上面也刚刚说了，博主此前是用的WIN7刚换的WIN10系统嘛。

具体办法：

下载这个东西： Awesomium 1.6.6 SDK

下载完一路点安装就行。

遇到有2个点不了next的时候，是有一个需要同意用户协议，勾选上同意就可以下一步了，还有一个是要选择安装类型，安装类型的在左边点击最顶部的typical标准套餐就可以了。

最后，重启MarkdownPad就解决问题了。

总结

还是那句老话了，遇到问题时善用搜索工具，先自己实践的尝试去解决，对于重要的文件一定要多备份数据，最好在备份数据上动手，以免损坏源文件什么的。

咱有一个问题就解决一个问题，不能让问题堆积如山，2333…

捋清思路之后，有针对的各个击破，问题就简单了

感谢阅读，么么扎~~

新年快乐！😁