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

scaffoldme

v1.3.1

Published

An easy-peasy scaffolding CLI tool

Downloads

3

Readme

Scaffoldme

Scaffoldme is an experiment to build a simple scaffolding app, kinda like Yeoman, but easier to create templates for.

Making a template

Making a template is really easy:

You simply create a folder with the name of the template you want to use, create subdirectories for each variant of the template (if you don't want to use any variants just place all your files inside the default subdirectory) and you're done!

Each variant folder should contain a _variables.js file, which just contains a module.exports statement with a list of all the variables you want to be replaced in your file, for example:

module.export = [
  "author",
  "version",
  "name"
]

In your files you'll then be able to use variables by writing the variable name in upper case and enclosing it in square brackets: [VARIABLE].

Here's what the file structure of a template should look like:

<template>
     ├─── default
     |    ├─── _variables.js
     |    └─── src
     └─── <variant>
          ├───_variables.js
          └───src

CLI Commands

Once you replicate the template file structure on your system, you can add a template to the CLI by going into the template directory and using the command scaffoldme add --name <name>, where the default template name is the working directory's name.

Once you've done that you can scaffold the template into your directory with the command scaffoldme create <template> --variant <variant>, which will ask you the value for each variable in your _variables.js file and will substitute them into the template files. If no variant parameter is provided the command automatically assumes you want to use the default variant.

To list all of the templates you have registered and their variants you can simply run the command scaffoldme list, and everything will be outputted. If you get any errors, you might want to check your file structure: it's likely you forgot to put your template in a default variant folder!

To remove a template you can use the command scaffoldme remove <template>, which will unregister a template from the CLI. If no template argument is provided the CLI will automatically assume the template name is the working directory's name.

Have fun!