You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 1, 2020. It is now read-only.
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.6 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.1 but none is installed. You must install peer dependencies yourself.
audited 2007 packages in 3.052s
found 0 vulnerabilities
PS F:\ayzb\we\wechaty-getting-started> npm install wechaty-puppet-padchat
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.6 but none is installed. You must install peer dependencies yourself.
[email protected]
updated 1 package and audited 2007 packages in 5.366s
found 0 vulnerabilities
PS F:\ayzb\we\wechaty-getting-started>
The text was updated successfully, but these errors were encountered:
PS F:\ayzb\we\wechaty-getting-started> npm install
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.6 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.1 but none is installed. You must install peer dependencies yourself.
audited 2007 packages in 3.052s
found 0 vulnerabilities
PS F:\ayzb\we\wechaty-getting-started> npm install wechaty-puppet-padchat
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of wechaty-puppet@^0.15.6 but none is installed. You must install peer dependencies yourself.
updated 1 package and audited 2007 packages in 5.366s
found 0 vulnerabilities
PS F:\ayzb\we\wechaty-getting-started>
The text was updated successfully, but these errors were encountered: