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

markdownlint-rule-github-internal-links

v0.1.0

Published

Custom markdownlint rule for checking internal links like those generated by Github

Downloads

277

Readme

markdownlint-rule-github-internal-links

Custom markdownlint rule for checking internal links like those generated by Github's Markdown processor. Specifically, this rule checks that internal links (of the form #anchor) match the anchors generated by this anchor generation code, or manually inserted anchors via name or id attributes.

For example, in this README.md, the link #configuration will not report an error, while the link #config will. In addition, the links #enable-rule and #add-package will match the manually inserted anchors below, while the link #add-rule will report an error.

Usage

  1. Add this package to your project:

    npm install -D markdownlint-rule-github-internal-links
  2. Enable the rule:

Configuration

You can pass in a setting of verbose: true to make this plugin display every anchor link it computes and every link it tests. This can be useful for debugging your anchor links, when it's hard to guess how many -s to add. See sample .markdownlint.yaml (for cli or cli2) and sample .markdownlint-cli2.jsonc (for cli2).

More Complex Example

A more complex example is the header above, which produces the link #-more-complex-example.