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
Add more tests
np rolls back repo even when nothing has been committed
Support GPG password prompt
Ensure no extraneous files get published
Add tests for pre-publish tasks
Add tests for utility files
Gracefully handle branch not having an upstream
Enable 2FA when publishing a new package
"Verify user is authenticated" Credentials Issue
npm seems to use different git setup
Add tests for the config
Add support for setting flags globally and as config in package.json
Fails on first time start with git rev-list error
Possible to use new "npm ci" during release?
Can't publish the initial version as a prerelease
Rollback git operations on np fail
Accept the 2FA (otp) token after 6 characters
Ignore check for npm name when `--no-publish`
Use new-github-release-url to give link to prefilled release notes w/commits
Newly publishing a public scoped package does not include the `--access public` flag
Ability to publish without a version bump
On first publish, `np` says `bin` and license files won't be published, and ignores `main` and `package.json`
Tag flag is not working
npm 9.0.0 Support?
Publish fail using "np --any-branch"
NIT: Yarn warning np@7.6.2: The engine "git" appears to be invalid.
np is including irrelevant yarn.lock files
Received an error on first run: "pattern is too long"
The project rolled back to previous state on "Publishing package using Yarn"
Suddenly hangs on "Publishing package using npm"
Yarn: Publish won't recognize I'm logged into npm
Publishing of subfolders is broken since npm v8.5
Publishing wrong version with yarn and ng-cli
Golang alternative tool
Add flag to skip "Unclean working tree" check
Create release draft error
Ensure CI has passed
Broken for me when installed via Yarn
Option to not hijack child process streams
Handle network failures gracefully
GitHub login prompt not displayed
npm version is failing and I have the lastest
Login to private registry fails (Verdaccio, Nexus, …)
Fails to run with Yarn Nightly
allow publishing current version without increment, to workaround issue with prerelease versions and --no-publish with CI/CD
Ability to pass in sign flag to Git
Check npm or yarn audit before publishing
First publish fails if it's a prerelease
Sanity check for non-existant files
Security leak on package `got`
Custom tag template
How to use with multiple npm accounts
Does not understand `"files"` starting with `/`; thinks files will be omitted
Github Action
Sign git tags
JavaScript heap out of memory with an unreleased npm package
contents does not work when defined in config file
np and pre-commit will report an error when used together
Will np start depending on GitHub’s autogen’d Release notes?
support for pnpm
Incorrect file list when `.gitignore` and `.npmignore` differ
NP command has been waiting
Why it is wait long time after I run np
Strange behaviour with npm organisations
Add flag to avoid pushing the tag commit back to the repo
Error "pattern is too long"
CVE-2021-3807 at multiple library levels
Provide option to skip push tag
How can I use pnpm rather than npm?
Handle a missing `repoUrl`
np prerelease error: Unexpected token u in JSON at position 0
Set git tag template format
git ls-remote fails when using password protected ssh-key
support custom the version preid for interactive CLI
Build artifacts after bumping version inside package.json but before commit/tag
gitignore-like configuration file - Suggestion name "npignore"
Release draft is silently failed for shorthand Github values
Git fatal error: Could not read from remote repository when I run np
--tag option not working
Question: drop Node v10? v12? (CVE-2022-33987)
Promote NP related tools
.np-config/(np-config in package.json) getting ignored
Freezes on git activity
Failure to Publish Specific Version since v9.0.0
Allow `publishConfig.registry` to be npm default registry
Allow `publishConfig.access` to "public" even the package is not scoped
Not detecting yarn berry correctly
Rollbacks on git operations does not happen on failed publish.
deprecated dependencies: inflight, rimraf and glob
Add support for Bun
`getNpmPackageAccess` not reading `publishConfig`
`npm whoami` fails when `.npmrc` has custom registry
No commit created, no tag, no push
"Unsupported engine" error swallowed
np formats the `package.json` file upon use.
README `packageManager` link goes to a page without any information
OSMILE
Support OIDC publishing
Cannot run `np` globally on Node.js v20.12.2
Run `npm login` if not authenticated?
Commit range does not use the previous tag to generate release notes
Clear output on successful publish
CLI default flags is overriding local `np-config.jon` flags
Verbose mode
Prevent accidentally dropping support for older Node.js versions in a non-major version bump
Wrong assumption in Node version check for version below 1.0.0
np fails instantly if `pack` script fails
`np --release-draft-only` broken in v11
Accept --dry-run as a synonym (alias) to --preview
Move prerequisite+git checks before the wizard
Run `npm install` even on `--skip-cleanup`
`prerelease` should not default to `x.0.0-rc.0`, but `x.0.0-0`
Bad pre-requisite check for second prerelease (v4.0.0-1)
Feature request: Adding Canary Credentials to detect compromise
np error ERR_REQUIRE_ESM
Replace `listr` dependency
List files in a less verbose way by auto-grouping them
Error with npm v9+: `npm access 2fa-required is not a valid access command`
use pnpm
np v8 breaking bug: NPM version check fails when `npm` is not specified in engines field in package.json
Won't work if dependencies are not defined
unable to publish package using Yarn -- cannot read properties of undefined (reading 'pipe')
np command not execute
SyntaxError: Unexpected token '&&='
How to publish with --provenance?
Proposal: backwards-compatible compression before publish
Unable to publish preview (`publish.getPackagePublishArguments` is not a function)
Allow creating a GitHub draft release without generating release notes
ls-collaborators is not a valid access command with npm v9
np output command error
Security vulnerability on package `got`. Consider dependency tree shaking
Provide a way to silently approve in advanced files that won't be part of the published package
`ENOWORKSPACES` when publishing from workspace
np command extremely slow
how to hook in to publish a bundle with injected version
Doesn't include `dist` folder
np hangs while publishing
after published, print the npm url
When prepublishOnly script fails, Git operations are not rolled back
Support pnpm in 2024?
Issue with Dependency Packages on publish
Consider dropping `ow`
Duplicate Tag + Release created without `v` Prefix
np with npm 10.5.1: Failed to parse output of npm pack
Husky prepare script breaking np
Duplicate console output
Ensure dependencies are compatible with the supported Node.js version
`yarn publish` errors are opaque
[feat] create release draft option (e.g. `np release-draft <version>`) would trigger release page
Can't execute np due to heroku
np@5.2.1 - Command failed with exit code 1
Private root package prevents non-private subdirectory from being published
Failed within `np`,`scoped package`,`publishConfig.registry`
Semver prerelease format is invalid
Add a real prepublish hook?
Don't use `npm ci` if lockfiles are ignored by git
Adding typing to the project
`np` does not actually ensure "that there are no unpulled changes"
Possibility to set branch name?
Script is stuck at "publishing package usage npm" (keeps loading)
Empty files or .npmignore warning on private package
Display more information on failure
Bumping version using npm fails
Only publish from a specific branch
HTML tags in commit messages disappearing
np is always asking for OTP
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
`np` crashes on Node.js versions earlier than v9.7.0
Documentation: Clear instruction on CI publishing of private packages
ERR 400 2FA when no 2fa is configured on account/repo
[CI/CD] "No commits found since previous release, continue?" is always thrown
Publishing to GitHub Packages yields 405 (Method Not Allowed)
Ensure that required files are packaged
Git Permission Denied
Stuck at "Publishing package using npm"
Publish publicly prompt does not publish the package publicly
possible to configure prompt of public publishing?
`np` doesn't actually check for unpulled changes (before showing version selection in interactive mode)
Publishing to github registry fails
Git "no unpulled changes" not working?
v5 not compatible with verdaccio anymore?
Standardizing package.json "np.contents" publish dir
np does not publish to npm, no error, no OTP code asked
customuse git tag
Problems after running cleanup
Version based on current head branch and commit
Throw Cannot read property 'type' of null for private git repo
Help wanted
Issues with adopting to a private package
Doesn't finish "Publishing package" step even though repo shows a successful publish.
GitHub Enterprise URLs aren't supported
Show a notification when OTP is required
`np prerelease` should default to `--tag next`
Show versions in non-interactive mode (e.g. `$ np minor`)
Verify sourcemaps before publishing
Command failed with exit code 128
Broken w/ private Verdaccio reigstry - npm access ls-collaborators fails
New package instructions don't work
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
Version 5.1 reports “Aborted!” when it should complete successfully
np 5.1 instantly crashes on macOS
Ability to bump the version number of --contents not the root package.json
"upstream branch not found; not pushing." errors
--no-tests flag does not work
Fatal Error on start: unknown revision or path not in the working tree.
"Bumping version using npm" runs forever
Automatic Semver
`--no-publish` still ask for tag
Np skipping the draft release step
`npm version` errors on files generated during `npm test`
Broken update notification in 7.0.0
Question: Do you keep prerelease tags?
Feature Request: Custom commit message input
"Show files added since..." feature should ignore the `.github` directory
yolo in package.json is ignored
Option to print actual commands to be run (similar to --preview)
Lint before publishing?
np fails to publish package on verdaccio due to missing collaborators file?
Confusing ignored files prompt
Not working / no interactive feedback
Yarn: np hangs when installed as a local devDependency
Good way to create draft releases (Question)
Tailor `yarn.lock` error based on whether it is gitignored
If run as global script, local config is ignored.
Stuck at the "Prerequisite check" stage
Package publishing partially fails when running tasks
git tag the latest commit instead of making a new one
Pushing commit straight after publish reduces package quality score when commit triggers build using CI
2FA fails with 400 Bad Request on initial package publish
`np` interactive prompt exits at version selection with no output/error
✖ glob pattern string required with np 7.5.0 on clean repo
✖ Cannot read property 'length' of undefined
Support Yarn >= v2 (berry)
Feature Request: --remote option
The following new files will not be part of your published package
np is ignoring .d.ts in dist folder
Customize tag name
CLI flag for `--skip-unclean`
`need auth` error when calling `np` via npm script
403 Forbidden when publishing subdirectory
Check for scopes
Executing `np --version` tries to execute typical np executiion
Move to ESM format
Unexpected end of JSON input
Support ESM only for the config file
Call to "ls-collaborators" fails with Nexus Package Manager
np --release-draft-only has several issues (wrong tag, "missing repoURL" error)
Removes trailing newline in package.json
Unable to publish package on GitHub registry
503 Service Unavailable error on 2FA
Stuck on prerequisite check
Cannot use as global install after local install
Ctrl+C during np cli exits with status 0
Confusing publish message about scoped repos
GitLab release draft
preid from .npmrc is not respected when drafting the github release
Have a short product description in the README.md file
Automatic stash and pop?
Private repository doesn't support "whoami"
np is turning on two-factor authentication and we don't want it
np tries to publish to npm twice, then fails and rollback
NP does not prompt for release draft
Ability to skip tests (not cleanup)
yarn workspaces
Release draft uses wrong tag
Open release notes in the editor before opening GitHub
"npm whoami" check fails if np is ran in an npm-script by yarn
Incorrectly showing "You must specify a dist-tag using --tag when publishing a pre-release version."
Bumping version using npm keep runnning
Option to disable 2FA
contents flag does not get respected in latest version
error on publish
np for monorepos
Can't rollback if the repo does not have a tag
Make np more configurable and customizable
Specify test command to run
The releaseDraft step appears to be skipped in my setup
np is just publishing the package.json and README.md
Add npmClient option
Hanging on publishing to npm
Restrict semver increments
Bump and publish a specific tag
Not possible to specify a custom version via the interactive UI
© 2019 BoostIO, Inc.