npm-name-cli: Error on some names

HTTPError throws when checking some package names via this cli-package. Like this:

~ $ npm-name f
HTTPError: Response code 404 (Not Found)
    at stream.catch.then.data (/usr/local/lib/node_modules/npm-name-cli/node_modules/squatter/node_modules/got/index.js:182:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

f is real npm package.

When using API from npm-name it will be all right for this package:

const nn = require('npm-name');
await nn('f') // false

I thing it is a bug.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 15 (8 by maintainers)

Commits related to this issue

Work around npm registry breakage See https://github.com/sindresorhus/npm-name-cli/issues/9 — committed to sholladay/squatter by sholladay 6 years ago

Most upvoted comments

check-npm-dependents

good idea, @astur.

Is anyone else sad that it’s 2018, npm Inc has been a funded company for 5 years, and there’s still no API for this kind of thing? Seems ridiculous that we have to scrape the website for this info.

zeke on May 25, 2018

@sholladay No problem, I can change scra to got if you want it.

astur on Aug 20, 2018