Welcome to wechat-bot Discussions!

[wangrongding]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[WiZ1314]

你好，我在运行npm i的时候出现了以下问题
`npm ERR! code 1
npm ERR! path D:\wechat-bot-main\node_modules\wechaty-puppet-wechat\node_modules\puppeteer
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node install.js
npm ERR! ERROR: Failed to set up Chromium r982053! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
npm ERR! Error: read ECONNRESET
npm ERR! at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
npm ERR! errno: -4077,
npm ERR! code: 'ECONNRESET',
npm ERR! syscall: 'read'
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\wlz57\AppData\Local\npm-cache_logs\2022-12-11T12_23_34_816Z-debug-0.log`
请问要怎么解决

[wangrongding]

参考这个方案。
#54 (comment)

[wangrongding]

切换下镜像源，用我的 prm-cli 也很方便，你这个应该是依赖没正常安装

[WiZ1314]

我换成啦taobao还是不行
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: < 18.1.0 is no longer supported
npm ERR! code 1
npm ERR! path D:\wechat-bot-main\node_modules\wechaty-puppet-wechat\node_modules\puppeteer
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node install.js
npm ERR! ERROR: Failed to set up Chromium r982053! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
npm ERR! Error: read ECONNRESET
npm ERR! at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
npm ERR! errno: -4077,
npm ERR! code: 'ECONNRESET',
npm ERR! syscall: 'read'
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\wlz57\AppData\Local\npm-cache\_logs\2022-12-11T13_14_54_013Z-debug-0.log

[wangrongding]

先参考这个方案。
#54 (comment)

[1huangzixian]

跑起来了 但是没有二维码 貌似还报错了

[wangrongding]

先参考这个方案。
#54 (comment)

[1huangzixian]

11:19:54 ERR PuppetWeChatBridge start() exception: Error: An executablePath or channel must be specified for puppeteer-core
11:19:54 ERR PuppetWeChat initBridge() exception: An executablePath or channel must be specified for puppeteer-core
11:19:54 ERR PuppetWeChat initBridge() this.bridge.stop() rejection: Error: no page
GError: An executablePath or channel must be specified for puppeteer-core
at assert (C:\Users\1\Desktop\wechat-bot-main\node_modules\puppeteer-core\lib\cjs\puppeteer\util\assert.js:28:15)
at ChromeLauncher.launch (C:\Users\1\Desktop\wechat-bot-main\node_modules\puppeteer-core\lib\cjs\puppeteer\node\ChromeLauncher.js:69:36)
at PuppeteerNode.launch (C:\Users\1\Desktop\wechat-bot-main\node_modules\puppeteer-core\lib\cjs\puppeteer\node\PuppeteerNode.js:154:105)
at PuppeteerExtra.launch (C:\Users\1\Desktop\wechat-bot-main\node_modules\puppeteer-extra\dist\index.cjs.js:128:41)
at async Bridge.initBrowser (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/bridge.js:109:23)
at async Bridge.start (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/bridge.js:48:28)
at async PuppetWeChat.initBridge (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/puppet-wechat.js:176:13)
at async PuppetWeChat.onStart (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/puppet-wechat.js:69:23)
at async PuppetWeChat.start (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/state-switch/dist/esm/src/service-ctl/service-ctl.js:62:17)
at async PuppetWeChat.start (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet/dist/esm/src/mixins/se ' at async PuppetWeChat.initBridge (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/puppet-wechat.js:176:13)\n' +
' at async PuppetWeChat.onStart (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet-wechat/dist/esm/src/puppet-wechat.js:69:23)\n' + ' at async PuppetWeChat.start (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/state-switch/dist/esm/src/service-ctl/service-ctl.js:62:17)\n' + ' at async PuppetWeChat.start (file:///C:/Users/1/Desktop/wechat-bot-main/node_modules/wechaty-puppet/dist/esm/src/mixins/service-mixin.js:18:13)'}

[wangrongding]

先参考这个方案。
#54 (comment)

[Giftedvon360]

Hello everyone I'm new here

[wangrongding]

😀 welcome

[Giftedvon360]

Thanks man how are you?

[fexx-f]

No veo errores evidentes en el código que has proporcionado. La sintaxis de la función getChatGPTReply parece correcta, y la lógica de la función también parece estar implementada de manera adecuada. Sin embargo, hay algunos aspectos que se podrían mejorar en el código:

La función getChatGPTReply usa el objeto env para obtener valores de variables de entorno, pero no maneja errores que puedan ocurrir al cargar el archivo .env. Una forma de manejar estos errores sería utilizando un bloque try-catch en torno a la llamada a dotenv.config().
La función getChatGPTReply hace una llamada a console.log para imprimir el contenido y la respuesta de ChatGPT en la consola. Esto puede ser útil para depurar la aplicación, pero en un entorno de producción, es mejor evitar imprimir información sensible en la consola. En su lugar, se podría utilizar un sistema de registro para registrar esta información de manera segura.
La función getChatGPTReply no maneja errores que puedan ocurrir al enviar un mensaje a ChatGPT o al verificar la autenticación del usuario. Esto puede causar que la aplicación falle de manera inesperada si se produce un error. Una forma de manejar estos errores sería utilizando un bloque try-catch en torno a la llamada

[wangrongding]

Thx~🌸 I will improve it

[DTG1795705671]

因为终端的问题，二维码乱码，我通过二维码下面的url在浏览器上打开了二维码，但是在手机w微信扫码后显示

[oldfishoh]

这个问题是因为你扫码太慢了，它已经发送新的二维码给你了 你要扫最新的

可以用vscode的终端来运行这样出来的二维码可以直接扫 就不需要再复制链接到网页了

[metecanpolat1]

@wangrongding