I wasn't logged in, but the changes were committed & tagged, so when running <code

publish cannot be ran again of npm publish fails about oao HOT 5 CLOSED

ericclemmons commented on May 24, 2024

publish cannot be ran again of npm publish fails

from oao.

guigrpa commented on May 24, 2024

Oh, that happens to me every once in a while as well. I usually run then npx oao all "npm publish". Maybe that helps you too?

from oao.

guigrpa commented on May 24, 2024

Thinking about it, maybe oao should check whether you're logged in (npm whoami?) before proceeding with the publish, what do you think?

from oao.

ericclemmons commented on May 24, 2024

That'd be the most side effect way, I think. On May 7, 2018 8:25 AM, "Guillermo Grau Panea" <[email protected]> wrote: Thinking about it, maybe oao should check whether you're logged in (npm whoami?) before proceeding with the publish, what do you think? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7TmDCE234IHcCXd60H-lu9ep21SmHks5twGd6gaJpZM4T0Qux> .

from oao.

guigrpa commented on May 24, 2024

Did you try the workaround I proposed?

from oao.

ericclemmons commented on May 24, 2024

That works!

On Mon, May 7, 2018, 9:28 AM Guillermo Grau Panea ***@***.***> wrote: Did you try the workaround I proposed? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7TusYINro3D0kdxvx-2HQ0u4g5uWLks5twHYhgaJpZM4T0Qux> .

from oao.

Recommend Projects