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

page-crafter

v1.0.1

Published

Page Crafter =======================

Downloads

2

Readme

Page Crafter

A tool for simply templating content pages using handlebars templating syntax with partials support.

Usage

pagecraft <dir> [options]

All files with a .handlebars extension will be run through the handlebars templating engine.

Any handlebars files with a leading _ underscore in the name will be registered as partials and not available in the final output.

All other files will be copied as-is to the output directory.

Options

| option | Description | |---------------------|---------| | -h,--help | help message | | -o,--out | Specify 'out' directory; default 'dist' | | -p,--params | Specify a YAML parameter file to be used as template context | | -c,--clean | Remove the 'out' directory before build | | -v,--version | Print version information |

Example

Given the following input directory structure:

website/
├── css/
│   ├── bootstrap.min.css
│   └── bootstrap-theme.min.css
├── js/
│   └── bootstrap.min.js
├── shared-partials/
│   ├── _navbar.html.handlebars
│   └── _footer.html.handlebars
├── index.html.handlebars
└── about-us.html.handlebars

A YAML parameter file named web-params.yml at the same level as website/ with the following contents:

---
sales_phone: 555-555-5555
sales_email: [email protected]

And running the following command:

pagecraft website/ -o dist/ -p web-params.yml

The following will occur:

  1. All files in css/ and js/ will be copied as-is to a new dist/ folder
  2. Partials named shared-partials/_navbar.html and shared-partials/_footer.html will be registered and available to be used in the index.html.handlebars and about-us.html.handlebars files as {{> shared-partials/_navbar.html }}. Notice that they are namespaced by their relative folder.
  3. The sales_phone and sales_email contents of web-params.yml will be available as context for each template.
  4. An index.html and about-us.html will be created in the dist/ folder after running through the handlebars templater with all available partials and context parameters.

The output will be:

dist/
├── css/
│   ├── bootstrap.min.css
│   └── bootstrap-theme.min.css
├── js/
│   └── bootstrap.min.js
├── shared-partials/
├── index.html
└── about-us.html