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

@tdjsnelling/ssg

v1.0.0

Published

ssg is a tiny Markdown → HTML static site generator.

Downloads

10

Readme

ssg

ssg is a tiny Markdown → HTML static site generator.

Install

Install ssg with

npm i -g @tdjsnelling/ssg

or

yarn global add @tdjsnelling/ssg

Usage

ssg only requires a path to the directory you wish to build.

ssg .

Markdown files will be compiled to HTML and all other static assets will be copied over to the build directory. HTML is run through prettier to ensure built files remain human readable and editable.

Optionally, you can tell ssg to serve the build and watch for changes with the --serve or -s option. By default the server runs on port 3000, this can be changed with the --port or -p option.

ssg . -s -p 5000

ssg will automatically rebuild files as and when it detects changes.

Options

Each markdown file can have an 'options' section before the content, to configure the build process. This section is enclosed in double-percent symbols, %%.

The existing options are as follows:

  • title: the to include in the page head
  • style: relative path to a CSS or SASS/SCSS file to include on the page. SASS/SCSS is automatically transpiled
  • math: if yes, include KaTeX rendering support on the page
  • code: if yes, include syntax highlighting support on the page
  • highlight: the syntax highlighting theme to use. should be the name of a highlight.js theme, otherwise default is used

Example

This README is built in the example folder. See the built page here.