-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Object message has no method 'replace'?? #871
Comments
Ref #857 (comment) |
@tommy351 Thx!!! Why should it happens? is it about the branch replacement? |
This was referenced Jun 30, 2023
This was referenced Nov 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once I type $sudo hexo d or with --debug, it shows
[error] 01:27:03.774 TypeError: Object message has no method 'replace'
TypeError: Object message has no method 'replace'
at Object.exports.parse (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/parser.js:437:19)
at parse (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:343:19)
at Object.precompile (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:473:23)
at Object.compile (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:588:16)
at exports.commitMessage (/usr/local/lib/node_modules/hexo/lib/plugins/deployer/util.js:17:15)
at /usr/local/lib/node_modules/hexo/lib/plugins/deployer/github.js:114:26
at /usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:610:21
at /usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:249:17
at iterate (/usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:149:13)
at /usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:160:25
I've checked the parser.js, everthing looks fine. I don't know why it will alert that has no method 'replace'?
here is my hexo version:
hexo: 2.8.3
os: Darwin 14.0.0 darwin x64
http_parser: 1.0
node: 0.10.32
v8: 3.14.5.9
ares: 1.9.0-DEV
uv: 0.10.28
zlib: 1.2.3
modules: 11
openssl: 1.0.1i
The text was updated successfully, but these errors were encountered: