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

lvlup-utils

v0.0.2

Published

Proceso de transpilación + build: - Primero convertimos ts a js - build - Análisis estático: - Determinar las dependencias que está usando nuestro proyecto - Eliminar dependencias importadas que no se estén usando : TreeShaking (Dead code elimination)

Readme

Notas de clase

Proceso de transpilación + build:

  • Primero convertimos ts a js
  • build
  • Análisis estático:
    • Determinar las dependencias que está usando nuestro proyecto
    • Eliminar dependencias importadas que no se estén usando : TreeShaking (Dead code elimination) https://www.patterns.dev/vanilla/tree-shaking
    • Minificar
    • Archivo .js .cjs /dist /build

Dependencias necesarias

  1. npm i -D @types/node vite-plugin-dts
  • Pasos:
    • crear vite.config.ts
    • entry point para el arbol de dependencias
    • plugin para generación de types
    • Configuración de modulo en package.json
      • eliminar private true para poder publicar en registry

ESLINT

Es una herramienta open source enfocada en el proceso de linting "reglas" para ECMAScript.

  • Mostrar errores de sintaxis
  • Mostrar errores de buenas prácticas
  • Mantener estilo consistente (espaciado, imports, comillas, etc)

Dependencias

npm init @eslint/config
npm i -D eslint-plugin-simple-import-sort // configurar import y export de archivos

Import aliases

  npm i -D vite-tsconfig-paths

Modificar archivos tsconfig y vite.config.ts

Husky

Ejecutar scripts en diferentes estadios del flujo. Debe ser un repositorio válido.

git init
npx husky-init && npm i
npx husky add .husky/pre-commit "npm run lint"
npx husky add .husky/pre-push "npm run build"

Flujo ideal

  • V1

    • Codear una feature
    • Cambiar la versión del package json
    • Deberíamos correr test y eslint
    • hacer la build manual / automatica
    • deberíamos publicar en npm / yarn / etc
  • V2

    • Codear una feature
    • Cambiar la versión del package json
    • Deberíamos correr test + eslint
    • hacemos un push a una branch feature de github
    • review del PR
    • Merge del PR contra rama estable
    • GITHUB ACTION para hacer test , build y publish en npm

Commitlint

npm install -D @commitlint/config-conventional @commitlint/cli
echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js
npx husky add .husky/commit-msg  'npx --no -- commitlint --edit ${1}'

Pruebas unitarias

Conjunto de pruebas automatizadas (idealmente) que verifican que cada parte del codigo funciona correctamente

yarn add -D vitest