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

@mgalbis/remark-prefix-links

v1.0.2

Published

Prefix relative paths with a prefix URL.

Downloads

10

Readme

Build Coverage

remark-prefix-links

remark plugin to prefix relative paths with a prefix.

Installation

npm install @mgalbis/remark-prefix-links

Usage

Say we have the following file example.md:

[I'm an inline-style link](https://www.example.com)
[I'm an inline-style link with title](example.com "Example's Homepage")
[I'm a reference-style link][Arbitrary case-insensitive reference text]
![I'm a relative reference to an image](static/image.png)
[You can use numbers for reference-style link definitions][1]
Or leave it empty and use the [link text itself].

[arbitrary case-insensitive reference text]: static/link
[1]: static/link
[link text itself]: static/link

And our module example.js looks as follows:

const fs = require('fs')
const html = require("remark-html")
const remark = require("remark")
const plugin = require("@mgalbis/remark-prefix-links")
remark()
    .use(plugin, { pathPrefix: "test" })
    .use(html)
    .process(fs.readFileSync('example.md'), (err, file) => {
        if (err) throw err
        console.log(String(file))
    })

Now running node example.js yields:

<p>
  <a href="https://www.example.com">I'm an inline-style link</a>
  <a href="test/example.com" title="Example&#x27;s Homepage">I'm an inline-style link with title</a>
  <a href="test/static/link">I'm a reference-style link</a>
  <img src="test/static/image.png" alt="I'm a relative reference to an image">
  <a href="test/static/link">You can use numbers for reference-style link definitions</a>
  Or leave it empty and use the <a href="test/static/link">link text itself</a>.
</p>

API

remark.use(plugin[, options])

  • options.pathPrefix (required) - the path prefix that will be prepended to the begging of links.

Contributions

If you are interested in contributing to this project, please open an issue with a description of what you would like to add.

License

MIT © Maria Galbis