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

@yankeeinlondon/link-builder

v1.2.1

Published

adds contextual classes and features to links in documents used in vite-plugin-md

Downloads

647

Readme

Link Builder for vite-plugin-md

This repo is hosted externally but provided as a "built-in" part of the vite-plugin-md plugin.

Provides a power-user features for the links in your vite-plugin-md documents.

Usage

// vite.config.js
import Markdown from 'vite-plugin-md'
import { link } from '@yankeeinlondon/link-builder'

export default defineConfig({
  // ...
  plugins: [
    Markdown({ builders: [link()] }),
  ],
})

Default Behavior

With no configuration passed into link() you will get the following behavior:

  • Class Attribution
    • internal vs. external links
    • any reference to a http (versus https:) resource will be given the class "insecure"
    • if a non-HTTP protocol is specified (e.g., mailto:, file:, etc.)
    • if a document has an href directly to an image, document, code the content type will be be given a class
    • anchor links (aka, links to the same page) will also get a class
  • VueJS Router
    • any internal link will be converted from <a href="xyz"> link to a <router-link to="xyz" > and the relative paths needed to produce a valid route will be calculated for you
  • Link Cleanup
    • in vs-code (and various other editors), linking between two Markdown files is supported with autocomplete but the completed link maps directly to the markdown FILE (aka, has .md extension)
    • this is desireable for file based linking but needs to be tidied up when converting to HTTP based navigation
    • The default configuration will:
      • remove index.md fully just leaving the "directory" or "route"
      • remove .md from all other links

Configuration

The configuration is all done with a single dictionary configuration object passed into link( config ) and is fully typed (LinkOptions). Rather than documenting this twice, just refer to the typed documentation in the config object.