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

fpavon-ee-shared

v1.0.65

Published

Carpeta compartida entre servicios de Expediente Electronico

Readme

📦 Publicación de paquetes en npm (con 2FA)

Este documento explica cómo publicar paquetes en npm cuando la cuenta tiene autenticación en dos factores (2FA) habilitada, incluyendo el flujo completo de trabajo.


🚀 Flujo completo para publicar una nueva versión

1. ✏️ Actualizar versión

Modificar la versión actual por la nueva en package.json:

{
  "version": "1.0.62"
}

📌 Seguir semver:

  • patch → fixes (1.0.61 → 1.0.62)
  • minor → features (1.0.x → 1.1.0)
  • major → breaking changes

2. 📤 Subir cambios al repositorio

git add .
git commit -m "chore: bump version to 1.0.62"
git push

👉 Esto asegura trazabilidad antes de publicar


3. 🏗️ Build del paquete

npm run build

👉 Genera los archivos que realmente se publican (ej: /dist)


4. 📦 Publicar en npm

Opción A — Con OTP

npm publish --otp=123456

Opción B — Con token (recomendado)

npm publish

🔐 Configuración de 2FA

Problema común

npm ERR! 403 Forbidden - Two-factor authentication required

👉 npm exige 2FA también al publicar


✅ Soluciones

🥇 Usar OTP

npm publish --otp=123456

🥈 Usar token con bypass 2FA (recomendado)

1. Crear token

https://www.npmjs.com/settings/tokens

  • Tipo: Automation
  • Con Bypass 2FA activado

2. Configurar en local

npm config set //registry.npmjs.org/:_authToken=TU_TOKEN

3. Publicar

npm publish

🔍 Verificaciones útiles

Usuario actual

npm whoami

Registry

npm config get registry

Debe ser:

https://registry.npmjs.org/

🧠 Problemas comunes

❌ Error 404

Not found - PUT https://registry.npmjs.org/paquete
  • No tienes permisos
  • El nombre ya existe

❌ Error 403

2FA required
  • Usar --otp
  • o token con bypass 2FA

⚠️ Warning config

Unknown user config "config"

👉 No bloquea publicación


🚀 Recomendación

👉 Usar token con bypass 2FA Evita tener que ingresar OTP cada vez.


📌 Resumen rápido

| Paso | Acción | | ---- | ------------------------------- | | 1 | Subir versión en package.json | | 2 | Commit + push | | 3 | npm run build | | 4 | npm publish |


🛠️ Comandos clave

npm login
npm whoami
npm run build
npm publish
npm publish --otp=XXXXXX
npm config set //registry.npmjs.org/:_authToken=TOKEN