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

secullum-i18n

v1.1.1

Published

Library to add i18n capabilities

Readme

Secullum I18n

Biblioteca para adicionar capacidades de internacionalização (i18n) aos seus projetos JavaScript.

Como atualizar a versão do pacote npm

Atualizando a versão do pacote npm

  1. Escolha o tipo de incremento de versão:

    • Patch (correções):
      npm version patch
    • Minor (novas funcionalidades, sem breaking changes):
      npm version minor
    • Major (mudanças incompatíveis):
      npm version major
  2. O comando acima irá:

    • Atualizar o campo version no package.json.
    • Criar um commit com a mensagem padrão.
    • Criar uma tag git correspondente à nova versão.
  3. Envie as alterações para o repositório remoto:

    git push origin main

    Substitua main pelo nome do seu branch principal, se for diferente.


Publicando o pacote no npm

  1. Certifique-se de que está logado no npm:
    npm login
  2. Execute o build do projeto (se necessário):
    npm run build
  3. Publique o pacote:
    npm publish

Resumo

  • Sempre use npm version para atualizar a versão.
  • Use git push origin main para enviar branch e tags juntos.
  • Use npm publish para publicar a nova versão no npm.
  • As tags são importantes para releases e integração contínua.