sindresorhus/
A better `npm publish`
USD raised
Recent activities
Missing `test` run script should not fail `np` when using Yarn
All private scoped packages detected as non-published
Add a `--preview` flag to dry-run np
Enable 2FA when publishing a new package
Gracefully handle branch not having an upstream
Add tests for pre-publish tasks
Ensure no extraneous files get published
np rolls back repo even when nothing has been committed
"Verify user is authenticated" Credentials Issue
Can't publish the initial version as a prerelease
Possible to use new "npm ci" during release?
Fails on first time start with git rev-list error
Add support for setting flags globally and as config in package.json
Add tests for the config
Rollback git operations on np fail
Accept the 2FA (otp) token after 6 characters
Use new-github-release-url to give link to prefilled release notes w/commits
Ignore check for npm name when `--no-publish`
Issues with adopting to a private package
possible to configure prompt of public publishing?
Version based on current head branch and commit
Problems after running cleanup
customuse git tag
np does not publish to npm, no error, no OTP code asked
Publishing to github registry fails
Throw Cannot read property 'type' of null for private git repo
`npm version` errors on files generated during `npm test`
Np skipping the draft release step
`--no-publish` still ask for tag
"Bumping version using npm" runs forever
Fatal Error on start: unknown revision or path not in the working tree.
--no-tests flag does not work
"upstream branch not found; not pushing." errors
np 5.1 instantly crashes on macOS
Version 5.1 reports “Aborted!” when it should complete successfully
Check if package contains any files before publishing
New package instructions don't work
Broken w/ private Verdaccio reigstry - npm access ls-collaborators fails
`np` crashes on Node.js versions earlier than v9.7.0
Only publish from a specific branch
Bumping version using npm fails
Empty files or .npmignore warning on private package
Script is stuck at "publishing package usage npm" (keeps loading)
Adding typing to the project
Duplicate console output
Add a real prepublish hook?
Semver prerelease format is invalid
Failed within `np`,`scoped package`,`publishConfig.registry`
Private root package prevents non-private subdirectory from being published
np@5.2.1 - Command failed with exit code 1
Can't execute np due to heroku
[feat] create release draft option (e.g. `np release-draft <version>`) would trigger release page
`yarn publish` errors are opaque
Ensure dependencies are compatible with the supported Node.js version
Publish publicly prompt does not publish the package publicly
Stuck at "Publishing package using npm"
Publishing to GitHub Packages yields 405 (Method Not Allowed)
Documentation: Clear instruction on CI publishing of private packages
HTML tags in commit messages disappearing
Create release notes even if pushing the branch failed
np hangs at various steps of the publish pipeline
np is always asking for OTP
Ability to bump the version number of --contents not the root package.json
Release draft uses wrong tag
Ability to skip tests (not cleanup)
NP does not prompt for release draft
np tries to publish to npm twice, then fails and rollback
np is turning on two-factor authentication and we don't want it
Automatic stash and pop?
Removes trailing newline in package.json
preid from .npmrc is not respected when drafting the github release
Confusing publish message about scoped repos
Cannot use as global install after local install
Stuck on prerequisite check
503 Service Unavailable error on 2FA
Unable to publish package on GitHub registry
Have a short product description in the README.md file
Not possible to specify a custom version via the interactive UI
Bump and publish a specific tag
Restrict semver increments
Hanging on publishing to npm
Add npmClient option
np is just publishing the package.json and README.md
The releaseDraft step appears to be skipped in my setup
Specify test command to run
Open release notes in the editor before opening GitHub
Can't rollback if the repo does not have a tag
np for monorepos
error on publish
Option to disable 2FA
Bumping version using npm keep runnning
Incorrectly showing "You must specify a dist-tag using --tag when publishing a pre-release version."
"npm whoami" check fails if np is ran in an npm-script by yarn
`need auth` error when calling `np` via npm script
2FA fails with 400 Bad Request on initial package publish
Pushing commit straight after publish reduces package quality score when commit triggers build using CI
git tag the latest commit instead of making a new one
Package publishing partially fails when running tasks
If run as global script, local config is ignored.
Tailor `yarn.lock` error based on whether it is gitignored
Good way to create draft releases (Question)
Broken update notification in 7.0.0
Confusing ignored files prompt
Feature Request: Custom commit message input
np --release-draft-only has several issues (wrong tag, "missing repoURL" error)
Executing `np --version` tries to execute typical np executiion
© 2019 BoostIO, Inc.
IssueHunt
