npm Could not pack error about semantic-release HOT 6 CLOSED

Hey @tlvince,

really cool to see you're giving semantic-release a try.
I've looked into this and currently I have no idea where it is coming from.

After the Determining new version there would need to be at least one other log message before the actual publishing (that might internally pack) happens. And even then, why would packing fail.

Can you try clearing caches on travis and then rerun? Unfortunately that's the only starter for debugging I can give you atm. Please report back in this issue if you have found anything.

from semantic-release.

@tlvince

I can reproduce this now, so it's definitely a semantic-release bug. Currently investigating where this is coming from, maybe a new npm version.

from semantic-release.

@tlvince Okay I think I know what's happening now.
npm publish starts the spinner which eats up all the log output on travis.
Because of this the expected 'Nothing changed. Not publishing.' simply isn't shown even though everything is fine.
The latest npm changed the error message a bit, so npm ERR! addLocalDirectory Could not pack is the expected output for an aborted publish.

Can you please verify this by adding this to your travis.yml

before_deploy:
 - npm config set spin false --global

from semantic-release.

Thanks for tracking that down @boennemann. I can confirm disabling the spinner gives an expected log output and this was a false alarm.

Just adding a note to the readme giving the heads up that this is normal behaviour or to disable the spinner (if npm >= v1.4.11?) would suffice.

from semantic-release.

@tlvince Thanks for checking that. This started happening only with more recent npm versions.
I'll add a note once I'm back in my home wifi ;)

from semantic-release.

I'd suggest to put that in the default .travis.yml, with a comment containing the URL of this issue.

By the way, I got bit by this issue (I think) when I tried to do the first deploy to npm. The package did not yet exist. I expected that in that case, semantic-release would create a 1.0.0 as a default?

from semantic-release.