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

innew-cli

v0.3.0

Published

CLI para estandarizar branch + workspace VTEX.

Readme

Innew Workflow CLI

CLI para estandarizar el flujo de trabajo en proyectos VTEX IO:

  • Genera branches con el formato definido: tipo/descripcion#TEAM-ID.
  • Crea y cambia automáticamente al workspace VTEX correspondiente.
  • Evita malas prácticas (nombres inconsistentes, workspaces incorrectos).

📦 Requisitos


⬇️ Instalación

Opción 1: Instalar desde NPM (Recomendado)

# Instalar globalmente
npm i -g innew-cli

# O usar sin instalar
npx -y -p innew-cli innew --help

Opción 2: Instalación local (para desarrollo)

# Clonar el repositorio
git clone https://github.com/tu-org/innew-workflow-cli.git
cd innew-workflow-cli

# Instalar dependencias
npm install

# Vincular globalmente para desarrollo
npm link

🔄 Actualizar o reinstalar en local

Si ya tenés el CLI instalado localmente y querés actualizarlo:

# Desvincular la versión anterior
npm unlink -g innew-cli

# Limpiar dependencias y cache
rm -rf node_modules package-lock.json

# Reinstalar dependencias
npm install

# Volver a vincular
npm link

🗑️ Desinstalar

Si instalaste desde NPM:

npm uninstall -g innew-cli

Si instalaste en local (con npm link):

# Desvincular el paquete global
npm unlink -g innew-cli

# Opcional: eliminar el repositorio clonado
cd ..
rm -rf innew-workflow-cli

🚀 Uso

Comando: innew init

Crea una nueva branch y workspace siguiendo el estándar del equipo.

innew init

Opciones CLI (saltean prompts):

innew init -t feature -d "nueva-funcionalidad" -T IDE -i 1234

| Flag | Descripción | Ejemplo | |------|-------------|---------| | -t, --type | Tipo de branch | feature, fix, chore, hotfix, refactor | | -d, --desc | Descripción breve | nueva-funcionalidad | | -T, --team | Código de equipo | IDE | | -i, --id | ID del ticket | 1234 |

Resultado:

  • Branch: feature/nueva-funcionalidad#IDE-1234
  • Workspace: nuevafuncionalidadide1234

Comando: innew branch

Muestra las últimas 3 branches del historial y permite cambiar rápidamente.

innew branch

Opciones:

innew branch --last    # Usa la más reciente sin prompt
innew branch --show    # Solo lista, sin cambiar nada
innew branch --all     # Usa historial global en vez del repo actual

Comando: innew commit

Crea commits formateados usando el contexto de la branch actual.

innew commit

Opciones CLI:

innew commit -t fix -m "corrige error en el footer"

| Flag | Descripción | Ejemplo | |------|-------------|---------| | -t, --type | Tipo de commit | feat, fix, refactor, style, docs, test, chore | | -m, --message | Descripción del cambio | corrige error en el footer |

Formato del commit:

[fix] (IDE-1234): corrige error en el footer

Si la branch no sigue el formato estándar:

[fix]: corrige error en el footer

🔧 Configuración (.innewrc.json)

Podés crear un archivo .innewrc.json en la raíz de tu proyecto para establecer valores por defecto:

{
  "defaultType": "feature",
  "defaultTeam": "IDE"
}

📂 Historial

El CLI guarda un historial global de branches en:

  • Linux/Mac: ~/.config/innew/history.json
  • Windows: %APPDATA%\innew\history.json

🛠️ Desarrollo

# Clonar repo
git clone https://github.com/tu-org/innew-workflow-cli.git
cd innew-workflow-cli

# Instalar dependencias
npm install

# Vincular para desarrollo
npm link

# Probar comandos
innew init
innew branch
innew commit

# Ver ayuda
innew --help