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

@weh/matter

v1.1.0

Published

⚗ Front matter parsing plugin for the weh static site generator

Downloads

2

Readme

Features

  • Extract YAML metadata (Front Matter) from text files within the weh files array
  • Custom filter functions to include or exclude files from transforms

Installation

npm install --save @weh/matter

Usage example

const weh = require('@weh/weh')
const matter = require('@weh/matter')

// enter our main function:
// the main function should be an async function so that
// it automatically returns a promise
weh(async site => {
  // we register our plugin...
  site.use(matter)
  // ...and initiate the build process
  return site
})

Filter example

You can pass a custom filter as an option to matter to include or exclude files.

A filter is a function that takes the arguments file, options, and files. file is the current file, options is the options object passed to matter, and files is the entire array of files created by weh.

When the filter function returns true, matter applies its transforms to the current file object. Otherwise the file object remains unchanged.

The default filter in matter always returns true, so the transform will be applied to every file:

function filter (file, options, files) {
  return true
}

This is how you could use a filter to only apply matter to files ending with .md:

const weh = require('@weh/weh')
const matter = require('@weh/matter')

// custom filter function
// returns true if file path ends with '.md'
function myCustomFilter (file, options, files) {
  return file.path.endsWith('.md')
}

weh(async site => {
  // we register the matter plugin with our custom filter function...
  site.use(matter, {filter: myCustomFilter})
  // ...and initiate the build process
  return site
})

Options Example

matter uses [gray-matter](http://npm.im/gray-matter) for parsing metadata. All options of gray-matter are also available in matter.

This is what a plugin call with custom options would look like:

const weh = require('@weh/weh')
const matter = require('@weh/matter')

// we define our options object...
const myMatterOptions = {
  delims: '~~~'
}

weh(async site => {
  // ...and pass it to the use method
  site.use(matter, myMatterOptions)
  return site
})

How does it work?

matter extracts any Front Matter from the contents property of a file object and writes it to its metadata property.

Given the following text file:

---
title: Greeting
---
Hello World

The resulting weh file object would be:

contents: 'Hello World',
metadata: {
  title: 'Greeting'
}

Maintainers

Code of Conduct

This repository operates under the weallbehave Code of Conduct. Its contents can be found in CODE_OF_CONDUCT.md.

License

MIT (see LICENSE document)