Maybe we should consider using package for a better publish experiences?

[Albert-Gao]

Something like np ? Very interactive, but seems it is too strict, so we need to make sure our example work with that.

Or any other suggestion is welcome.

[vaibhavmule]

Looks like a good idea.

[Albert-Gao]

Thanks for the backing, @vaibhavmule I tried np in my own package, has some problems with promise handling, already got some issues on its list, don't know when will be fixed, will watch for it or try to find a new one.

[vaibhavmule]

what exactly issue you are facing? You tried with this project or another package of yours.

[Albert-Gao]

I tried that np when I tried to publish my own package: veasy

2 Problems:

1. after changing that version number from old to new, it will still show the successful message as old ver published

2. will tag but won't publish since always ends with error because of the promise issue which like in this issue, I use jest though

I published a new issue there with all the npm error log, hope it helps: https://github.com/sindresorhus/np/issues/192

[vaibhavmule]

It's good that you have raised the issue, I have tried simulating the bug and trying to fix, no luck as of now.

[Albert-Gao]

really thanks!

it would be good if you can reproduce that issue. I don't even know if it's a universal problem or not. or just because not compatible with some of the packages we are using. for instance, the first log is for rimraf.

[vaibhavmule]

Can you please check it as np has released 2.16.1

source: https://github.com/sindresorhus/np/pull/195

[Albert-Gao]

Thanks for the info, will try, but seems not that positive according to this

[Albert-Gao]

Works for me now!

[Albert-Gao]

Very nice experiences, try the new npm run pub, np works pretty well now

[vaibhavmule]

Okay cool.