Perfect, your call! It’s yours to do as you please now. Don’t forget to remove me as a maintainer if you end up using it.

My understanding is that the only way you can use `npx skeleton` is by publishing your CLI tool on that package, but then you’d have 2 packages for the same CLI if you want to keep using the one within your namespace.

Ah, npx is a bit different indeed. That one does fetch remotely unless you have that bin defined in `node_modules/.bin/` (i.e. if you have installed @skeletonlabs/skeleton-cli beforehand.

You’d need to use it like this `npx @skeletonlabs/skeleton-cli`

No worries at all Hugo, happy to help ✌🏼

Yep, that must be why you keep hitting mine. Installing yours and/or uninstalling mine should then start hitting yours as long as you set `bin` in your package.json

CLI bin is 100% local, NPM won’t look through all of the existing packages with the same bin name.

If someone installs multiple packages with the same bin name, the last one installed will be used.

I think we can safely say that the `skeleton` package isn’t a going to be a treat here 😄

Oh, well, then the package itself isn’t relevant or needed for you. All you need is to add `bin` to your package.json file. See dev.to/rameshpvr/bi...

Fun fact: I know this because I did this in the past for www.npmjs.com/package/reac... which I used to own and transferred to the React team 🙃

If you click “show deprecated versions” and scroll all the way down to 0.1.0, that’s a library I built 10 years ago 😅

Only way is to `npm deprecate skeleton "[Deprecation notice message]"` and then make sure you `npm publish` a new version that is higher than the current 0.1.2

Current versions will forever be visible as deprecated versions, but there’s no way around that.

Maintainer invitation sent 🫡

Can you give me your NPM username? I will need to add you as a owner and the you can do as you please with it. Either here or by email if you prefer ([email protected])

Absolutely. Will look into how I can free the npm package and let you know 🙃