Post

Oh no. I managed to nerd snipe myself into Yet Another Side Project™ … again. Noooooo. #TooManyIdeas

… and upon publication it turns out the package name and netlify domain are already taken 🫤 So I generated a second side project named `namecheck` that allows me to check whether a name is available or not … and of course the `namecheck` name itself is ALSO already taken 😆

8/10/26, 2:16 pm0 reposts13 likes

Thomas Broyer

@tbroyer.ltgt.net

AFAIK the rules for NPM about what they consider "similar names" aren't public, so such tool will have false positives (negatives?) anyway.

Bramus

@bram.us

Yeah, package names can still be revoked for that reason. But still it gives you a hint upfront about whether you should continue with the name or start thinking of something else.

Bramus

@bram.us

Inspired by `caniuse` I renamed the namecheck project to `caniname` caniname.netlify.app Currently checks Netlify subdomain names and NPM package names. Any other checks to add?

caniname.netlify.appcaniname – Check Project Name Availability Across Netlify, NPM, and MoreA zero-dependency CLI tool and Node.js library to check project name availability across Netlify, NPM, and more.

Snugug

@snugug.bsky.social

Can you check firebase subdomains too?

Bramus

@bram.us

Ask your agent and file a PR ;) (The project is constructed in such a way that each check is a separate file on disk)

Jaap Stronks

@jaapstronks.nl

Well… domain names, obv? I made one for myself with a @transip.bsky.social token to find available domain names for side projects. I just feed it a thousand or so possible domain names with all kinds of TLDs, and it churns through them to eventually present a quite short list of available domains