npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

kiss-sdd-skills

v0.2.0

Published

CLI para instalar as skills do projeto kiss-sdd-skills no Codex, Gemini CLI e Claude Code

Downloads

14

Readme

INSTRUCAO_NPM.md

Guia prático para publicar e atualizar seu pacote no npm.


1. PRÉ-REQUISITOS

Antes de publicar:

  • Conta no npm (https://www.npmjs.com/)
  • Node.js instalado
  • Projeto com:
    • package.json válido
    • campo "bin" configurado (para CLI)
  • 2FA habilitado na conta npm (obrigatório para publish)

2. LOGIN NO NPM

Execute:

npm login

Informe:

  • usuário
  • senha
  • código 2FA

3. VALIDAR O PACOTE ANTES DE PUBLICAR

Verificar problemas no package.json

npm pkg fix

Simular o pacote

npm pack

Isso gera um arquivo .tgz.

Teste:

npx ./nome-do-pacote-1.0.0.tgz install codex

4. PUBLICAR NO NPM

Primeira publicação:

npm publish --access public

Se não houver erro, o pacote estará disponível.


5. TESTAR PUBLICAÇÃO

Execute:

npx nome-do-pacote install codex

ou:

npx nome-do-pacote install gemini

6. ATUALIZAR O PACOTE

Toda atualização exige mudança de versão.


6.1 Atualizar versão

Patch (bugfix)

npm version patch

Minor (nova funcionalidade)

npm version minor

Major (quebra de compatibilidade)

npm version major

6.2 Publicar nova versão

npm publish

7. BOAS PRÁTICAS

  • Nunca sobrescreva versões já publicadas
  • Use versionamento semântico (semver)
  • Teste com npm pack antes de publicar
  • Documente mudanças (CHANGELOG)

8. COMANDOS ÚTEIS

Ver pacote publicado:

npm view nome-do-pacote

Despublicar (evitar em produção):

npm unpublish nome-do-pacote --force

9. FLUXO RECOMENDADO

  1. Fazer alterações no código
  2. Testar localmente (npm link)
  3. Rodar npm pack
  4. Testar com npx
  5. Atualizar versão (npm version)
  6. Publicar (npm publish)
  7. Testar novamente via npx

FIM