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

@genehack/my-eleventy-config

v1.0.0

Published

modular, configurable, reusable config for TypeScript-based 11ty sites

Downloads

7

Readme

my-eleventy-config

A modular, configurable, reusable configuration for 11ty-based websites that use TypeScript for configuration.

how to use this package

See 11ty's TypeScript docs on how to use a TypeScript-based configuration file for your 11ty site, then:

  1. In your individual site, add this package as a dependency:

    npm i --save @genehack/my-eleventy-config

    In your site's eleventy.config.ts file, import the module, override any of the default configuration values you'd like to change (see below for what those defaults are), and in the first line of the default export, load the plugin with a spread version of your config overrides and the intermediate: true flag:

    import eleventy from "@11ty/eleventy";
    import myConfig from "@genehack/my-eleventy-config";
    
    const myConfigConfig = {
      enableCssMinimization: false,
      passthrough: {
        dirs: ["fonts"],
        files: [],
      },
    };
    
    export default async function (config: eleventy.LocalConfig): Promise<void> {
      await config.addPlugin(myConfig, { ...myConfigConfig, immediate: true });
    
      // rest of your custom config goes here…
    }

default configuration

By default, the plugin provides this configuration:

{
  enableCssMinimization: true,
  enableDrafts: true,
  enableImageOptimization: true,
  enableScss: true,
  enableSyntaxHighlighting: true,
  feeds: {
    atom: false,
    json: false,
    rss: false,
  },
  markdownItOptions: {
    html: true,
    linkify: true,
    typographer: true,
  },
  passthrough: {
    dirs: [],
    files: [],
  },
  templateFormats: ["html", "md", "njk"],
}

TODO FIXME document what the options do

important note

Currently, because of the way config overrides are applied, if you override a top-level default, (e.g., passthrough), you must provide all the keys present in the default. For example, if you wanted to add an images directory to passthru:dirs, your config override would need to look like:

const myConfigConfig = {
  passthrough: {
    dirs: ["images"],
    files: [],
  },
};

Emitting the passthrough:files key will result in an error.