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

to-gatsby-remark-plugin

v0.1.0

Published

Convert remark plugins to gatsby remark plugins

Downloads

16,596

Readme

to-gatsby-remark-plugin

Convert remark plugins to gatsby remark plugins.

Installation

yarn add to-gatsby-remark-plugin
# npm install to-gatsby-remark-plugin

Why

Remark plugins are plugins that can be used with remark (unifiedjs), there are already tons of plugins in the community. Gatsby remark plugins are plugins that can only be used in Gatsby, which is capable of using some of the Gatsby's specific APIs and graphql interfaces. However, we don't usually need all those APIs in our remark plugins, sometimes the plugins just have to manipulate the AST.

gatsby-transformer-remark only supports passing Gatsby remark plugins. gatsby-plugin-mdx supports both Gatsby remark plugins and remark plugins with gatsbyRemarkPlugins and remarkPlugins options separately. However, gatsbyRemarkPlugins always have precedence over remarkPlugins, which makes it difficult to compose multiple plugins in specific order.

As a result, plugin authors tend to re-create a Gatsby remark plugin for every remark plugin. This is far from ideal. What if we can just convert our remark plugins into Gatsby remark plugins automatically? This is exactly what this package does!

Usage

For users

Create a file locally with the following code.

// gatsby-my-remark-plugin.js
const toGatsbyRemarkPlugin = require('to-gatsby-remark-plugin');
const myRemarkPlugin = require('my-remark-plugin');

module.exports = toGatsbyRemarkPlugin(myRemarkPlugin);

Reference this file when specifying in the gatsby remark configs.

// gatsby-config.js
module.exports = ({
  plugins: [
    {
      resolve: `gatsby-plugin-mdx`,
      options: {
        gatsbyRemarkPlugins: [
          {
            resolve: require.resolve(`./gatsby-my-remark-plugin.js`),
          }
        ]
      },
    },
  ],
});

For library authors

We can focus on creating the remark plugin, then add a sub-package just for Gatsby. Create a gatsby directory under the root directory with 2 files inside: package.json and index.js.

// gatsby/package.json
{
  "name": "gatsby-my-remark-plugin",
  "main": "index.js"
}
// gatsby/index.js
const toGatsbyRemarkPlugin = require('to-gatsby-remark-plugin');
const myRemarkPlugin = require('..');

module.exports = toGatsbyRemarkPlugin(myRemarkPlugin);

Then the users can just reference the Gatsby remark plugin via my-remark-plugin/gatsby.

// gatsby-config.js
module.exports = ({
  plugins: [
    {
      resolve: `gatsby-plugin-mdx`,
      options: {
        gatsbyRemarkPlugins: [
          {
            resolve: `my-remark-plugin/gatsby`
          }
        ]
      },
    },
  ],
});