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

@vinnyum/devto-publisher

v1.0.5

Published

Publishes posts from a git repository to dev.to, rewriting relative image links to GitHub raw URLs.

Readme

@vinnyum/devto-publisher

Una herramienta de línea de comandos para automatizar la publicación y actualización de artículos escritos en Markdown hacia DEV.to.

💡 ¿Qué hace?

Cuando escribes en Markdown localmente o en un repositorio Git, es común usar imágenes relativas como ![](./assets/screenshot.png). DEV.to no puede leer imágenes locales.

Esta herramienta:

  1. Analiza el frontmatter y el contenido de tu post.
  2. Reescribe todas las rutas relativas de imágenes (incluida la portada cover) para apuntar a la URL cruda de GitHub correspondientes en tu repositorio (raw.githubusercontent.com/...).
  3. Envía el post a la API de DEV.to como borrador (draft) o actualiza uno existente.

🚀 Instalación y Uso

Puedes usarla directamente con npx sin instalar:

npx @vinnyum/devto-publisher [options] <article_path>

Opciones de CLI:

  • -r, --repo <owner/name>: Repositorio en GitHub (ej. mi-usuario/mi-repo). Si se ejecuta dentro de un repositorio git local, la CLI intentará inferir este valor automáticamente leyendo la configuración remota.
  • -b, --branch <branch>: Rama de Git para resolver las URLs de imágenes (ej. main, develop). Si estás en git local, se inferirá la rama actual de forma automática.
  • -t, --token <token>: API Key de DEV.to. También se puede configurar a través de la variable de entorno DEVTO_TOKEN.
  • -i, --article-id <id>: ID del artículo en DEV.to. Proporciona esta opción si deseas actualizar un borrador/post existente en lugar de crear uno nuevo.

Ejemplo de uso:

npx @vinnyum/devto-publisher -t tu_token_de_devto -r aguilavajz/apex-insights articles/es/mi-articulo.md

📝 Licencia

ISC