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

blowtorch

v0.1.2

Published

Static site generator

Downloads

5

Readme

Blowtorch

NPM version Build status Code Climate Coverage Status Dependencies

This repository is for learning purposes. It may intentionally contain bugs or fail to function properly. The code may be purposefully difficult to read, contain syntax errors, or only be a partial solution. You should not base code off of this and absolutely should not use it in production.

blowtorch src dest

The expected setup of the src dir is to have the following:

  • A _pages directory
  • A _layouts directory

These directories are special and will be processed separately. All other files will be recursively copied to the destination directory.

Each file within _layouts is a named layout. It will be used as a template for each page. A layout should have a {{ content }} marker in it that will be replaced with the content of each page.

Each of the pages will be copied to the destination directory. The content will be embedded in the layout it specifies. Pages can specify both a layout and variables to use in a template via a configuration file. The configuration file should be the same name as the file, but with an underscore before it and a .json extension. For instance, blog.html would have a configuration file of _blog.json.

The _site.json file stored within the root of src will be used for the default configuration for each page.