sindresorhus/np

Issues

• Cannot run `np` globally on Node.js v20.12.2

  #747 opened 2 days ago by mesqueeb
  0

• np hangs while publishing

  #725 opened 6 months ago by holdenmatt
  4

• np with npm 10.5.1: Failed to parse output of npm pack

  #740 opened 2 months ago by karlhorky
  6

• Husky prepare script breaking np

  #742 opened 2 months ago by numfin
  3

• Duplicate Tag + Release created without `v` Prefix

  #738 opened 3 months ago by karlhorky
  10

• ls-collaborators is not a valid access command with npm v9

  #710 opened 9 months ago by reconbot
  5

• Doesn't include `dist` folder

  #719 opened 7 months ago by mahyarmirrashed
  5

• Consider dropping `ow`

  #732 opened 3 months ago by tommy-mitchell
  2

• Support pnpm in 2024?

  #729 opened 3 months ago by mmkal
  1

• Issue with Dependency Packages on publish

  #731 opened 3 months ago by ganeshsacharya
  0

• When prepublishOnly script fails, Git operations are not rolled back

  #728 opened 5 months ago by awmottaz
  0

• after published, print the npm url

  #727 opened 5 months ago by lovetingyuan
  2

• Open npmjs.com instead of asking for OTP

  #726 opened 6 months ago by fregante
  1

• Move to `listr2` when v6 is out of beta

  #684 opened a year ago by tommy-mitchell
  6

• npm 9.0.0 Support?

  #665 opened a year ago by karlhorky
  4

• how to hook in to publish a bundle with injected version

  #718 opened 8 months ago by JoernT
  1

• List files in a less verbose way by auto-grouping them

  #690 opened 7 months ago by Drarig29
  6

• np command extremely slow

  #717 opened 8 months ago by jonesy-b-dev
  7

• `ENOWORKSPACES` when publishing from workspace

  #715 opened 9 months ago by karlhorky
  1

• np error ERR_REQUIRE_ESM

  #712 opened 9 months ago by dimaskc
  2

• Provide a way to silently approve in advanced files that won't be part of the published package

  #713 opened 9 months ago by Asaf-S
  0

• np command not execute

  #699 opened a year ago by ChristianHardy
  3

• np output command error

  #711 opened 10 months ago by Mastrota
  0

• Allow creating a GitHub draft release without generating release notes

  #708 opened 10 months ago by sgarner
  0

• Unable to publish preview (`publish.getPackagePublishArguments` is not a function)

  #705 opened a year ago by timphillips
  1

• Proposal: backwards-compatible compression before publish

  #704 opened a year ago by EvanHahn
  2

• How to publish with --provenance?

  #701 opened a year ago by vitalets
  0

• unable to publish package using Yarn -- cannot read properties of undefined (reading 'pipe')

  #698 opened a year ago by eswat2
  6

• SyntaxError: Unexpected token '&&='

  #700 opened a year ago by doctor-zhaohai123123
  1

• np v8 breaking bug: NPM version check fails when `npm` is not specified in engines field in package.json

  #696 opened a year ago by JaneJeon
  2

• Won't work if dependencies are not defined

  #697 opened a year ago by hiigami
  0

• Error with npm v9+: `npm access 2fa-required is not a valid access command`

  #692 opened a year ago by karlhorky
  7

• use pnpm

  #694 opened a year ago by alphaleadership
  0

• Create release draft error

  #671 opened a year ago by dj-fiorex
  1

• Sanity check for non-existant files

  #674 opened a year ago by Richienb
  1

• On first publish, `np` says `bin` and license files won't be published, and ignores `main` and `package.json`

  #669 opened a year ago by rnwst
  3

• Security vulnerability on package `got`. Consider dependency tree shaking

  #678 opened a year ago by brunolnetto
  0

• Newly publishing a public scoped package does not include the `--access public` flag

  #660 opened a year ago by knpwrs
  2

• Golang alternative tool

  #676 opened a year ago by trungdlp-wolffun
  1

• Security leak on package `got`

  #675 opened a year ago by brunolnetto
  0

• Publish options `prepatch` and `prerelease` with error log.

  #673 opened a year ago by brunolnetto
  0

• Yarn: Publish won't recognize I'm logged into npm

  #657 opened a year ago by grosch
  3

• Publish fail using "np --any-branch"

  #664 opened 2 years ago by brunolnetto
  1

• NIT: Yarn warning np@7.6.2: The engine "git" appears to be invalid.

  #663 opened 2 years ago by meandavejustice
  1

• np is including irrelevant yarn.lock files

  #662 opened a year ago by tansanDOTeth
  1

• Tag flag is not working

  #668 opened a year ago by nicolascavallin
  1

• Ability to publish without a version bump

  #670 opened a year ago by illegalnumbers
  2

• Received an error on first run: "pattern is too long"

  #661 opened 2 years ago by tansanDOTeth
  3

• The project rolled back to previous state on "Publishing package using Yarn"

  #659 opened 2 years ago by github-mathieu-salles
  2

• Suddenly hangs on "Publishing package using npm"

  #658 opened 2 years ago by basvdijk
  1