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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gatsby-plugin-published

v1.0.1

Published

Gatsby plugin to add published and visible fields to nodes

Readme

gatsby-plugin-published

Gatsby plugin to add published and visible fields to nodes.

The published field indicates if the node must be published in a Production build. It is true if the post is not marked as draft and the date of the post is not in a future date.

The visible field indicates if the node must be visible. It can be used to filter nodes in queries to generate pages and lists.

These fields can be used to generate builds with or without draft pages to preview before publish pages.

Also it can be used to set a published date on a post to a future date and make that page be published only when running the build in the future. You can use this like a manual schedule for publishing a post.

Your queries can filter for the visible field to include/exclude pages.

In a production build only pages with the published field set to true will have the visible field true.

In a development build you can use the published field to know if a page is a draft (value set to false) and preview the result.

Install

npm install --save gatsby-plugin-published

or

yarn add gatsby-plugin-published

How to use

// In your gatsby-config.js
module.exports = {
  plugins: [
    {
      resolve: "gatsby-plugin-published",
      // Default values for options
      options: {
        // Field name on frontmatter to get the published date
        frontmatterDateFieldName: "date",
        // Field name on frontmatter to get the draft state (boolean)
        // Node is considered a draft if value is true
        frontmatterDraftFieldName: "draft",
        // Field name to add into node fields to set the visible state
        visibleFieldName: "visible",
        // Field name to add into node fields to set the published state
        publishedFieldName: "published",
        // Timezone for comparing dates
        timezone: "UTC",
        // Force draft nodes to be visible
        makeDraftVisible: false,
        // Valid nodes, any node type not in this list will be ignored
        validNodes: ["MarkdownRemark", "Mdx"]
      },
    },
  ],
}