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

unified-loader

v1.2.1

Published

a non-opiniated unified loader for wepack

Downloads

1

Readme

unified-loader

What

A webpack loader for processing files with unified, with a default setting to a "classic" remark-rehype pipeline.

Why

You could eventually use @mdx-js/loader for most of cases, but it won't allow to write <style> or <script> tags in your markdown.

How

In your webpack config, add a rule for markdown:

{
  test: /\.md$/,
  use: [{
    loader: 'unified-loader',
    options: {}
  }],
}

Options

Options can take 2 shapes:

type GenericOptions = {
  createPayload?: (mdContent: string) => string
  plugins?: UnifiedPlugin[],
}

type DefaultPipelineOptions = {
  createPayload?: (mdContent: string) => string
  remarkPlugins?: UnifiedPlugin[],
  rehypePlugins?: UnifiedPlugin[],
}

type Options = GenericOptions | DefaultPipelineOptions

Generic Options

This will give the most flexibility. You are expected to pass every plugin to process your file, which should leave the pipeline ending with a Value = { value: string } type.

Default Pipeline Options

This will probably be the most used. The structure is very familiar if you ever worked with remark/rehype tools. You are expected to give your remark and rehype plugins respectively in remarkPlugins[] and rehypePlugins[]

createPayload

You can modify directly the output of the loader here. The function will be called at the end of the loader to wrap the content of the file with custom code. There's already a reactPayload and stringPayload to help getting started.