sindresorhus/npm-name-cli

Issues

• `npm-name @org-name` is not working

  #31 opened a year ago by RobertSandiford
  2

• Hangs more often than not

  #30 opened a year ago by tommy-mitchell
  0

• handle errors more friendly

  #16 opened 6 years ago by ZYSzys
  2

• Switch from ES modules to be able to run on "npx"

  #29 opened 3 years ago by rodrigo-picanco
  1

• Node 14+ is unsupported!

  #28 opened 4 years ago by alflennik
  1

• Throws error via CLI

  #27 opened 4 years ago by eavichay
  1

• Misleading output for a taken name

  #26 opened 4 years ago by prantlf
  4

• Feature request: include (optional?) thesaurus of names relating to the search

  #22 opened 4 years ago by Robbie-Cook
  4

• Crashing on checking for availability

  #17 opened 4 years ago by arshadkazmi42
  4

• Name too similar

  #21 opened 5 years ago by kevincastejon
  1

• Incorrect link to organization

  #19 opened 5 years ago by forivall
  0

• Error on some names

  #9 opened 7 years ago by astur
  15

• You can do the same with bash and curl

  #12 opened 7 years ago by devlato
  2

• Invalid name reported as available

  #11 opened 7 years ago by astur
  4

• Update to reflect new registry typosquat restrictions

  #7 opened 7 years ago by ashleygwilliams
  2

• Name reported as available but can't be used in npm publish

  #10 opened 7 years ago by astur
  1

• can npm-name-cli expose API

  #8 opened 7 years ago by adriatic
  1

• Detect squatters

  #5 opened 7 years ago by sholladay
  2

• [Question] Harmony

  #1 opened 9 years ago by justinhelmer
  3