sindresorhus/
A better `npm publish`
USD raised
Recent activities
Husky prepare script breaking np
Duplicate Tag + Release created without `v` Prefix
Issue with Dependency Packages on publish
When prepublishOnly script fails, Git operations are not rolled back
Open npmjs.com instead of asking for OTP
np hangs while publishing
Doesn't include `dist` folder
how to hook in to publish a bundle with injected version
np command extremely slow
`ENOWORKSPACES` when publishing from workspace
Provide a way to silently approve in advanced files that won't be part of the published package
np output command error
Allow creating a GitHub draft release without generating release notes
How to publish with --provenance?
#### I'm opening this issue because:
Move to `listr2` when v6 is out of beta
Security vulnerability on package `got`. Consider dependency tree shaking
Security leak on package `got`
Sanity check for non-existant files
Publish options `prepatch` and `prerelease` with error log.
Create release draft error
Publish fail using "np --any-branch"
NIT: Yarn warning np@7.6.2: The engine "git" appears to be invalid.
Publishing of subfolders is broken since npm v8.5
Publishing wrong version with yarn and ng-cli
Add flag to skip "Unclean working tree" check
Release draft is silently failed for shorthand Github values
support custom the version preid for interactive CLI
git ls-remote fails when using password protected ssh-key
np prerelease error: Unexpected token u in JSON at position 0
Handle a missing `repoUrl`
Warn about new dependencies
contents does not work when defined in config file
Feature Request: --remote option
403 Forbidden when publishing subdirectory
Support ESM only for the config file
yolo in package.json is ignored
Option to print actual commands to be run (similar to --preview)
Lint before publishing?
Use Ink for the initial UI
contents flag does not get respected in latest version
Can't open github release page when release note is too long
EPERM when publishing public scoped package with 2FA
Command failed with exit code 128
Login to private registry fails (Verdaccio, Nexus, β¦)
--no-draft flag to avoid opening a GitHub release draft page
`np prerelease` should default to `--tag next`
No GitHub release draft flag
Support for Custom Publish Hooks
Show a notification when OTP is required
GitHub Enterprise URLs aren't supported
Handle no previous Git tags
Help wanted
Doesn't finish "Publishing package" step even though repo shows a successful publish.
Clarification on npm hooks documentation
Add `--no-git-tag-version` flag
Option to disable the git commit
Ensure that required files are packaged
Ensure CI has passed
Β© 2019 BoostIO, Inc.
IssueHunt
