Skip to content

arjunsajeev/npmcheck

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

npmcheck

Check npm package name availability from the command line.

Installation

Homebrew (macOS and Linux)

brew install arjunsajeev/tap/npmcheck

Go Install

go install github.com/arjunsajeev/npmcheck@latest

Download Binary

Download the latest binary from the releases page.

Usage

Check if one or more package names are available on npm:

npmcheck my-awesome-package another-package

Output:

  • ✅ indicates the package name is available
  • ❌ indicates the package name is already taken
  • ⚠️ indicates an error occurred while checking

Examples

# Check a single package
npmcheck my-new-package

# Check multiple packages at once
npmcheck pkg1 pkg2 pkg3

Development

Prerequisites

  • Go 1.25 or later

Building

Using just (recommended):

# Install just: brew install just (or see https://github.com/casey/just)

# List all available commands
just

# Build the binary
just build

# Run tests
just test

# Run all checks
just ci

Or using make:

# Build the binary
make build

# Run tests
make test

Or directly with Go:

# Build the binary
go build -o npmcheck

# Run tests
go test ./...

# Install locally
go install

Testing GoReleaser

To test the GoReleaser configuration locally without publishing:

goreleaser release --snapshot --clean

Releasing

This project uses GoReleaser for automated releases.

To create a new release:

  1. Tag the commit with a semantic version:

    git tag -a v1.0.0 -m "Release v1.0.0"
    git push origin v1.0.0
  2. GitHub Actions will automatically:

    • Build binaries for multiple platforms (Linux, macOS, Windows)
    • Create a GitHub release
    • Update the Homebrew formula

License

MIT

About

A simple Golang CLI which can check if an npm package exists

Resources

Stars

Watchers

Forks

Packages

No packages published