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

mdsg

v1.1.0

Published

markdown based static site generator

Downloads

6

Readme

mdsg - MarkDown Site Generator

Generates html from markdown using remark and rehype plugins from the unifiedjs ecosystem.

installation

npm i -g mdsg

usage

Convert *.md files in current directory to html and write to ./output/

mdsg

To specify input and output directories:

mdsg <inputDir> <outputDir?>

If only an input directory is specified, output will be written to <inputDir>/output/

print usage

mdsg --help

config

mdsg uses rc so you can set config in all the places rc looks.

Example config

{
  "assets": "./assets",
  "css": [
    "https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.2.0/styles/github-dark.min.css",
    "/assets/css/fonts.css",
    "/assets/css/styles.css",
    "/assets/css/theme.css"
  ],
  "injectCss": false
}

css

css links in head

The css array from config is used when linking to css files in the head tag of each html document. This is the default setting. A <link rel="stylesheet" href="/..."> tag is injected for each item in the array.

css style tags in head

To inject the css as style tags into each document:

mdsg --injectCss true

When injecting, the css is loaded from **/*.css files in the assets directory. They're lexicographically sorted by filename before being written into style tags in the head tag of each document.

assets

The assets directory contents are copied to the output directory.

skipping content

Directories or files with a leading underscore are skipped when reading content.

e.g. naming your output directory to _site/ would ensure it's skipped on a subsequent run.