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 🙏

© 2024 – Pkg Stats / Ryan Hefner

md-links003

v1.0.6

Published

Libreria para la validacion de links en archivos markdonw

Downloads

4

Readme

Markdown Links


md-links003 es una librería que lee y analiza archivos en formato Markdown, para verificar los links que contengan y reportar algunas estadísticas.

Instalación

npm i --g md-links003

Uso (CLI)

md-links PATH --stats --validate


  • Por ejemplo:

$ md-links ./some/example.md
ruta: ./some/example.md, link: http://process.com/2/3/, texto: process
ruta: ./some/example.md, link: http://google.com/ texto: Google

md-links PATH --validate

$ md-links ./some/example.md --validate ó --stats
ruta: ./some/example.md, link: http://process.com/2/3/, ok, 200, texto: process
ruta: ./some/example.md, link: https://ppt.net/algun-doc.html, fail, 404, ppt

md-links PATH --stats

$ md-links ./some/example.md --stats ó --validate
Total: 3
Unique: 3

md-links PATH --stats --validate

$ md-links ./some/example.md --stats --validate
Total: 3
Unique: 3
Broken: 1

Uso (API)

import mdLinks from 'md-links003';

mdLinks('./some/path', { validate: true })
  .then(links => console.log(links))
  .catch(error => console.log(error));

mdLinks(path, options)

Argumentos
  • path: Ruta absoluta o relativa al archivo o directorio. Si la ruta pasada es relativa, debe resolverse como relativa al directorio desde donde se invoca node - current working directory).
  • options: Un objeto con las siguientes propiedades:
    • validate: Booleano que determina si se desea validar los links encontrados.
Valor de retorno

La función debe retornar una promesa (Promise) que resuelva a un arreglo (Array) de objetos (Object), donde cada objeto representa un link y contiene las siguientes propiedades:

  • href: URL encontrada.
  • text: Texto que aparecía dentro del link (<a>).
  • file: Ruta del archivo donde se encontró el link.

Ejemplo

const mdLinks = require("md-links");

mdLinks("./some/example.md")
  .then(links => {
    // => [{ href, text, file }]
  })
  .catch(console.error);

mdLinks("./some/example.md", { validate: true })
  .then(links => {
    // => [{ href, text, file, status, ok }]
  })
  .catch(console.error);

mdLinks("./some/dir")
  .then(links => {
    // => [{ href, text, file }]
  })
  .catch(console.error);
$ md-links ./some/example.md --stats
Total: 3
Unique: 3

Flujograma


md-links

documentación técnica de la librería.

Metodología: Scrum

Duración: 3 semanas.

Github project

Recursos que se utilizaron

⌨️ < LABORATORIA /> Sobre mi 😊