sindresorhus/
A better `npm publish`
USD raised
Recent activities
Missing `test` run script should not fail `np` when using Yarn
Add more tests
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 utility files
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`
Make np more configurable and customizable
Verify sourcemaps before publishing
Show versions in non-interactive mode (e.g. `$ np minor`)
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
np does not publish to npm, no error, no OTP code asked
customuse git tag
Standardizing package.json "np.contents" publish dir
v5 not compatible with verdaccio anymore?
Git "no unpulled changes" not working?
Publishing to github registry fails
`np` doesn't actually check for unpulled changes (before showing version selection in interactive mode)
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
Automatic Semver
"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
publish: false has no effect in .np-config.json
np fails to create tag and add changes to git when versioning nested package.json
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
Display more information on failure
Empty files or .npmignore warning on private package
Script is stuck at "publishing package usage npm" (keeps loading)
Possibility to set branch name?
`np` does not actually ensure "that there are no unpulled changes"
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
Don't use `npm ci` if lockfiles are ignored by git
Publish publicly prompt does not publish the package publicly
Stuck at "Publishing package using npm"
Git Permission Denied
Publishing to GitHub Packages yields 405 (Method Not Allowed)
[CI/CD] "No commits found since previous release, continue?" is always thrown
ERR 400 2FA when no 2fa is configured on account/repo
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
503 Service Unavailable at step Enabling two-factor authentication
Fatal: No names found, cannot describe anything
User authentication fails
Scoped package publication detection fails
np is always asking for OTP
Ability to bump the version number of --contents not the root package.json
Release draft uses wrong tag
yarn workspaces
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
Private repository doesn't support "whoami"
Automatic stash and pop?
Removes trailing newline in package.json
preid from .npmrc is not respected when drafting the github release
GitLab release draft
Confusing publish message about scoped repos
Ctrl+C during np cli exits with status 0
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
Stuck at the "Prerequisite check" stage
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
Not working / no interactive feedback
Confusing ignored files prompt
np fails to publish package on verdaccio due to missing collaborators file?
"Show files added since..." feature should ignore the `.github` directory
Feature Request: Custom commit message input
Question: Do you keep prerelease tags?
Yarn: np hangs when installed as a local devDependency
np --release-draft-only has several issues (wrong tag, "missing repoURL" error)
Call to "ls-collaborators" fails with Nexus Package Manager
Support ESM only for the config file
Unexpected end of JSON input
Move to ESM format
Executing `np --version` tries to execute typical np executiion
Check for scopes
`np` interactive prompt exits at version selection with no output/error
CLI flag for `--skip-unclean`
Customize tag name
np is ignoring .d.ts in dist folder
The following new files will not be part of your published package
Support Yarn >= v2 (berry)
✖ Cannot read property 'length' of undefined
✖ glob pattern string required with np 7.5.0 on clean repo
Does not understand `"files"` starting with `/`; thinks files will be omitted
Custom tag template
Github Action
Sign git tags
JavaScript heap out of memory with an unreleased npm package
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
How to use with multiple npm accounts
How can I use pnpm rather than npm?
Set git tag template format
Build artifacts after bumping version inside package.json but before commit/tag
gitignore-like configuration file - Suggestion name "npignore"
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
Provide option to skip push tag
Yarn: Publish won't recognize I'm logged into npm
Suddenly hangs on "Publishing package using npm"
The project rolled back to previous state on "Publishing package using Yarn"
Newly publishing a public scoped package does not include the `--access public` flag
Received an error on first run: "pattern is too long"
np is including irrelevant yarn.lock files
npm 9.0.0 Support?
Tag flag is not working
On first publish, `np` says `bin` and license files won't be published, and ignores `main` and `package.json`
Ability to publish without a version bump
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
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
Golang alternative tool
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 '&&='
Proposal: backwards-compatible compression before publish
Unable to publish preview (`publish.getPackagePublishArguments` is not a function)
ls-collaborators is not a valid access command with npm v9
np error ERR_REQUIRE_ESM
after published, print the npm url
Support pnpm in 2024?
Consider dropping `ow`
np with npm 10.5.1: Failed to parse output of npm pack
Allow `publishConfig.registry` to be npm default registry
Add support for Bun
© 2019 BoostIO, Inc.
IssueHunt
