A better `npm publish`
Not possible to specify a custom version via the interactive UI
Have a short product description in the README.md file
Unable to publish package on GitHub registry
Cannot use as global install after local install
Ctrl+C during np cli exits with status 0
GitLab release draft
preid from .npmrc is not respected when drafting the github release
Removes trailing newline in package.json
Private repository doesn't support "whoami"
np is turning on two-factor authentication and we don't want it
Scoped package publication detection fails
User authentication fails
Fatal: No names found, cannot describe anything
503 Service Unavailable at step Enabling two-factor authentication
np hangs at various steps of the publish pipeline
Create release notes even if pushing the branch failed
Can't open github release page when release note is too long
ERR 400 2FA when no 2fa is configured on account/repo
[CI/CD] "No commits found since previous release, continue?" is always thrown
Git Permission Denied
Don't use `npm ci` if lockfiles are ignored by git
[feat] create release draft option (e.g. `np release-draft <version>`) would trigger release page
Display more information on failure
Only publish from a specific branch
EPERM when publishing public scoped package with 2FA
Check if package contains any files before publishing
np fails to create tag and add changes to git when versioning nested package.json
publish: false has no effect in .np-config.json
Command failed with exit code 128
NP does not prompt for release draft
`np` does not actually ensure "that there are no unpulled changes"
`np` doesn't actually check for unpulled changes (before showing version selection in interactive mode)
v5 not compatible with verdaccio anymore?
Git "no unpulled changes" not working?
Standardizing package.json "np.contents" publish dir
Make np more configurable and customizable
--no-draft flag to avoid opening a GitHub release draft page
Show versions in non-interactive mode (e.g. `$ np minor`)
`np prerelease` should default to `--tag next`
Verify sourcemaps before publishing
No GitHub release draft flag
Support for Custom Publish Hooks
Show a notification when OTP is required
GitHub Enterprise URLs aren't supported
Issues with adopting to a private package
Handle no previous Git tags
Doesn't finish "Publishing package" step even though repo shows a successful publish.
possible to configure prompt of public publishing?
Problems after running cleanup
Clarification on npm hooks documentation
Add `--no-git-tag-version` flag
Option to disable the git commit
np does not publish to npm, no error, no OTP code asked
Duplicate console output
Ensure that required files are packaged
Possibility to set branch name?
© 2019 BoostIO, Inc.