NPM Package Existence FAQs

Question 1

Can I check for scoped packages like @myorg/package?

Accepted Answer

Yes, the skill fully supports scoped packages. Simply provide the full name including the @ symbol and the scope prefix.

Question 2

How does the npm-exists skill check for package existence?

Accepted Answer

It performs a HEAD request to the official npm registry API. A 200 OK response indicates the package exists, while a 404 Not Found status suggests the name is available.

Question 3

What is the difference between npm-exists and npm-info?

Accepted Answer

The npm-exists skill is a lightweight check for presence/availability, whereas npm-info is intended for retrieving detailed metadata like versions, dependencies, and authors.

Question 4

Is the information provided by the skill always up to date?

Accepted Answer

Results are cached for one hour to optimize performance. However, you can use the --no-cache option to fetch the most current data directly from the API.

Question 5

Does it check for naming rule compliance?

Accepted Answer

Yes, the skill validates the package name against npm's official naming rules (e.g., URL-safe characters, length limits, and reserved names) before querying the registry.

NPM Package Existence

Key Features

Use Cases

NPM Package Existence

Key Features

Use Cases