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
I have a package with a prepublishOnly hook that does a bunch of checks. When I try to release a new version using grunt-release, I don't see any of the output of the hook, just the fact that it failed:
$ grunt release:minor
Running "release:minor" (release) task
>> bumped version of package.json to 0.18.0
>> staged package.json
>> Committed all files
>> created new git tag: 0.18.0
>> pushed to remote
>> pushed new tag 0.18.0 to remote
Warning: Failed when executing: `npm publish`
Use --force to continue.
Aborted due to warnings.
I can get the output by running npm publish directly, or just the prepublishOnly script itself, but it would be nicer if grunt-release could just proxy through the stdout/stderr output.
The text was updated successfully, but these errors were encountered:
I have a package with a
prepublishOnly
hook that does a bunch of checks. When I try to release a new version using grunt-release, I don't see any of the output of the hook, just the fact that it failed:I can get the output by running
npm publish
directly, or just theprepublishOnly
script itself, but it would be nicer if grunt-release could just proxy through the stdout/stderr output.The text was updated successfully, but these errors were encountered: