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

create-trindtech-app

v1.2.0

Published

Bootstrap público pro CLI privado @trindtech/create-next — configura o ~/.npmrc com PAT do GitHub Packages e roda o scaffolder

Downloads

777

Readme

create-trindtech-app

Bootstrap público pro CLI privado da Trindtech (@trindtech/create-next). Cuida do setup do token do GitHub Packages no primeiro uso e roda o scaffolder.

Uso

npx create-trindtech-app meu-projeto

Primeira vez: o wrapper detecta que falta o token do GHP, te orienta a gerar um Personal Access Token do GitHub (com scope read:packages), pede via prompt seguro, salva em ~/.npmrc e roda o scaffolder.

Vezes seguintes: pula direto pro scaffolder.

Pré-requisitos

  • Node 20+
  • Estar adicionado na org trindtech no GitHub
  • Personal Access Token com scope read:packages (o wrapper te orienta a gerar)

Como funciona

  1. ~/.npmrc e checa se tem //npm.pkg.github.com/:_authToken=<token> (não-vazio).
  2. Se faltar, mostra link pra gerar o PAT e pergunta o token (input mascarado, formato validado).
  3. Limpa scope routings legacy (@trindtech:registry=https://npm.pkg.github.com e @trindtech-private:registry=...) que versões anteriores do wrapper haviam adicionado — eles quebram projetos que dependem de @trindtech/utils (no npm público).
  4. Mescla com configs existentes no ~/.npmrc sem duplicar (idempotente). Permissão 0600.
  5. Executa npx --registry=https://npm.pkg.github.com --yes @trindtech/create-next <args> — força a busca do CLI no GHP sem rotear o scope globalmente.

Por que --registry e não scope routing?

Versões anteriores escreviam @trindtech:registry=https://npm.pkg.github.com no ~/.npmrc, mandando todo o scope @trindtech pro GHP. Isso quebrava projetos que dependem de @trindtech/utils (publicado no npm público). Agora o --registry afeta apenas a chamada do CLI; o scope @trindtech segue indo pro npm público no resto.

Segurança

  • O token nunca é ecoado no terminal nem logado.
  • O ~/.npmrc é gravado com chmod 0600 (só o dono lê).
  • Esse wrapper não tem o código do scaffolder — apenas a lógica de setup. Outsiders sem acesso à org Trindtech recebem 403 do GitHub Packages ao tentar usar.

Release

cd scripts/create-trindtech-app
# bump version no package.json
git tag wrapper-v1.1.1
git push origin wrapper-v1.1.1

Workflow .github/workflows/publish-wrapper.yml dispara e publica no npm público.