getting-started
getting-started copied to clipboard
No matching version found for wechaty-puppet-oicq@^1.10.2
No matching version found for wechaty-puppet-oicq@^1.10.2
是不是用了nrm ,把镜像切换到npm官方,不要用taobao的
是不是用了nrm ,把镜像切换到npm官方,不要用taobao的
又一个新的错误 ~/work/getting-started main npm install ✔ 16.13.1 18:26:53 npm ERR! code FETCH_ERROR npm ERR! errno FETCH_ERROR npm ERR! invalid json response body at https://www.npmjs.com/package/@chatie/eslint-config reason: Unexpected token < in JSON at position 1
npm ERR! A complete log of this run can be found in: npm ERR! /Users/long/.npm/_logs/2021-12-10T10_27_13_725Z-debug.log
问题非常多,也不知道是不是我本人问题,按照文档一步步来的,各种问题,这demo感觉很难跑通
Could you please let me know what "文档" did you read?
Could you please let me know what "文档" did you read?
- 建议官方的引导文档改下,那边是有问题的,是老的版本Wechaty v0.x,这个也是我后来看issues发现的
- 第二个我是按照你的这个demo的readme开始的,可能是我环境问题
另外我跑起来之后,虽然登录没问题,但是小号出现这个问题了
"Error: 你需要开通微信支付,才可继续操作。\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n at Bridge.readyAngular (file:///Users/long/work/getting-started/node_modules/wechaty-puppet-wechat/src/bridge.ts:321:15)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n at processTicksAndRejections (node:internal/process/task_queues:96:5)
- What is the URL of 官方的引导文档 you mentioned?
- Pull request is welcome to fix it
- Make sure you have a good network connection with your vps. A vps outside china is recommended.
@huan 大佬,我使用的环境是docker,跑了几个小时就会出现内存泄漏,按照找到已解决的issue一个参数-r --max-old-space-size
,我增加的位置是package.json里"demo": "cross-env NODE_OPTIONS=\"--no-warnings --loader=ts-node/esm\" node -r ts-node/register --max-old-space-size=1536 examples/ding-dong-bot.ts",
这一行,但是跑了几个小时还是会出现oom错误导致停止。
请问是我加错位置了吗?(我是用的go做client)
@iyzrj Please submit an new issue for your question with reproducible steps and the minimum code because it's not related to this issue.
No matching version found for wechaty-puppet-oicq@^1.10.2
我也遇到了这个问题,这个npm 依赖包 找不到 用的node版本是16.13.1 npm:8.3.0 你这个问题怎么解决的,能否解惑一下?谢谢!
未找到与 wechaty-puppet-oicq@^1.10.2 匹配的版本
我也遇到同样的问题,你是怎么解决的
@hyuankun2017 @brotherbear2008 try to remove all the npm mirror registry settings and try again.
If the problem solves, then it's because your npm mirror has outdated.