Menci / hexo-deployer-upyun

UPYUN deployer for Hexo.
GNU General Public License v3.0
22 stars 6 forks source link

请问这个和hexo版本有关系么 #6

Closed Emtemf closed 3 years ago

Emtemf commented 3 years ago

我升级成hexo5以后就报这个错误

undefined:1
<html>
^

SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>)
    at Object.utils.parseRes (D:\Blog_my\blog\node_modules\upyun\upyun\utils.js:188:21)
    at D:\Blog_my\blog\node_modules\upyun\upyun\api.js:138:28
    at IncomingMessage.<anonymous> (D:\Blog_my\blog\node_modules\upyun\upyun\utils.js:214:9)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Menci commented 3 years ago

https://github.com/abcdGJJ/hexo-deployer-upyun2019

试试这个

On Sat, Feb 6, 2021 at 05:49 kurumi notifications@github.com wrote:

我升级成hexo5以后就报这个错误

undefined:1

^ SyntaxError: Unexpected token < in JSON at position 0 at JSON.parse () at Object.utils.parseRes (D:\Blog_my\blog\node_modules\upyun\upyun\utils.js:188:21) at D:\Blog_my\blog\node_modules\upyun\upyun\api.js:138:28 at IncomingMessage. (D:\Blog_my\blog\node_modules\upyun\upyun\utils.js:214:9) at IncomingMessage.emit (events.js:203:15) at endReadableNT (_stream_readable.js:1145:12) at process._tickCallback (internal/process/next_tick.js:63:19) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or unsubscribe .
Menci commented 3 years ago

以及请不要在技术类讨论中到处用“老哥”这种强性别关联的称呼,谢谢。

Emtemf commented 3 years ago

感谢指导。很抱歉对您有造成困扰,还麻烦您将我的不当言论删除,谢谢大佬

------------------ 原始邮件 ------------------ 发件人: "Menci/hexo-deployer-upyun" <notifications@github.com>; 发送时间: 2021年2月8日(星期一) 中午12:53 收件人: "Menci/hexo-deployer-upyun"<hexo-deployer-upyun@noreply.github.com>; 抄送: "EMT"<1732483487@qq.com>;"Author"<author@noreply.github.com>; 主题: Re: [Menci/hexo-deployer-upyun] 老哥请问这个和hexo版本有关系么 (#6)

以及请不要在技术类讨论中到处用“老哥”这种强性别关联的称呼,谢谢。

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.