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

@mkverdu/npm-package

v1.0.1

Published

Basic nom package to be required by other application

Downloads

3

Readme

  • Crear la carpeta del proyecto en la ruta deseada

mkdir ruta/del/proyecto

  • Inicializar el proyecto
git init
npm init (responder con lo datos de configuración que se deseen)
  • Punto de entrada del proyecto

./src/index.js

  • Punto de ejecución al usar con la línea de comandos

./bin/global.js

  • Declaración del punto de ejecución en package.json (npm-package es el nombre del paquete)
"bin": {
"npm-package": "./bin/global.js"
},
  • Declaración de paquete con instalación global por defecto en package.json

"preferGlobal": true

Instalar de manera local

npm link

npm WARN [email protected] No repository field.

up to date in 0.42s
found 0 vulnerabilities

C:\Program Files\nodejs\npm-package -> C:\Program Files\nodejs\node_modules\npm-package\bin\global.js
C:\Program Files\nodejs\node_modules\npm-package -> C:\01_mobilots\02_projects\02_development\02_mobilots\01_dev\02_back\01_projects_git\tests\npm-package
  • Para actualizar la instalación del paquete ejecutar:

npm install

  • Desinstalar de manera local

npm unlink npm-package

Instalar en repositorio NPM

  • Crear una cuenta en NPM y logarse en el proyecto

$ npm login

Username: usuario
Password:
Email: (this IS public) [email protected]
npm notice Please check your email for a one-time password (OTP)
Enter one-time password from your authenticator app: 84689671
Logged in as mkverdu on https://registry.npmjs.org/.
  • Se puede hacer logout

npm logout

  • Definir el SCOPE 'activo' para poder subir un paquete a ese SCOPE (es lo mismo tnto para usuarios como para empresas)

npm init --scope=@usuario

  • Publicar el paquete con acceso público

npm publish --access public