-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare to publish to NPM as name wechaty-cli
#5
Comments
* add devops tools & clean code * add npm start for cli * 0.0.2 * add badges * add terminal image * fix: lint errors * 0.0.3 * feat: debug script, use forked blessed-contrib * 0.0.4 * chore: set vscode debugger to pwa-node Co-authored-by: chinggg <[email protected]>
Have you registered the npm account? Let's be ready to publish the cli to NPM as |
I have registered my npm account. Do I need to wait for meeting in the next week to publish to NPM? |
No you needn't. Please feel free to publish it by yourself, and then:
Please let me know after you have finished the above take, and then we will be able to setup the CI/CD with GitHub Actions for DevOps. |
Oh I unpublished the npm package because I find some errors, but now I have to wait for 24 hours. see npm/cli#958 |
We have published at https://www.npmjs.com/package/wechaty-cli |
Let's finish the NPM publishing before the mid-term.
You first need an npm account, then we can get this done in our next meeting.
The text was updated successfully, but these errors were encountered: