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

gatsby-source-netlify-cms

v0.10.5

Published

#### setting up your `gatsby-config.js`

Downloads

15

Readme

gastby-source-netlify-cms (Beta)

setting up your gatsby-config.js

Default setup uses the helper functions imported from the plugin.

const config = require(`config.json`); // netlify-cms config file (json format required)
const { createPluginPaths, createPluginOptions } = require('gatsby-source-netlify-cms');

module.exports = {
  plugins: [
    {
      resolve: "gatsby-source-netlify-cms",
      options: createPluginOptions(config)
    },
    ...createPluginPaths(config),
  ]
}

Note: The options.types of this plugin must match the options.name targets of the plugin paths being setup for the gatsby-source-filesystem plugin. If you plan to set these up manually, make sure to adhere to this naming convention or this plugin will ignore the nodes during onCreateNode.

Information

This configuration and plugin is going to do the following:

  • Create a valid options object for the source plugin using helper createPluginOptions
  • Sets up the gatsby-source-filesystem plugins to the paths of collections using helper createPluginPaths
  • Plugin will resolve the paths for the cms using the config during onPreBootstrap. If they don't exist, the plugin will create them.
  • Plugin creates the schema from the config using Gatsby's actions.createTypes during createSchemaCustomization and using the options.types created by createPluginOptions
  • Plugin creates the nodes during onCreateNode using the nodes created by gatsby-source-filesystem setup by createPluginPaths and the types configuration created by createPluginOptions
  • All the options and plugins can be configured manually if a more advanced naming of nodes and types is needed.