Open suntong opened 3 years ago
Thanks for the report!
I'd love to accept a PR for updating the dependencies of puppeteer from wechaty-puppet-whatsapp
An attempt to fix the issue is here https://github.com/wechaty/wechaty-puppet-wechat/pull/145. Please take a look. Thank you
1. Versions
2. Describe the bug
3. To Reproduce
4. Expected behavior
Single versions of puppeteer & Chromium requires & downloaded
5. Actual behavior
Two versions of puppeteer & Chromium required & downloaded, because
wechaty-puppet-whatsapp
is using an outdated versions of puppeteer thus chromium.6. Full Output Logs
Set env
WECHATY_LOG=silly
in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)We need full log instead of log screenshot or log fragments!
Show Logs
```shell rm -rf package-lock.json rm -rf node_modules $ npm install > puppeteer@7.1.0 install /path/to/wechaty-getting-started/node_modules/puppeteer > node install.js Downloading Chromium r848005 - 138.2 Mb [====================] 100% 0.0s Chromium (848005) downloaded to /path/to/wechaty-getting-started/node_modules/puppeteer/.local-chromium/linux-848005 > puppeteer@5.5.0 install /path/to/wechaty-getting-started/node_modules/whatsapp-web.js/node_modules/puppeteer > node install.js Downloading Chromium r818858 - 132.1 Mb [====================] 100% 0.0s Chromium (818858) downloaded to /path/to/wechaty-getting-started/node_modules/whatsapp-web.js/node_modules/puppeteer/.local-chromium/linux-818858 $ npm ls ├─┬ wechaty-puppet-wechat@0.28.0 │ ├─┬ puppeteer@7.1.0 │ ├─┬ puppeteer-extra@3.1.18 . . . └─┬ wechaty-puppet-whatsapp@0.2.3 ├─┬ puppeteer@5.5.0 . . . ```7. Additional context
Add any other context about the problem here.
[bug]