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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nekolu/simplegenerator

v1.0.2

Published

Generate template things simply and quickly.

Readme

Simple Generator

Generate template things simply and quickly.

Simple generator is just a little and simple generator. To create a template, you just need to run sg initTemplate and answer several questions.

You can also call sg initTemplate with arguments. First argument is template name, and second is path. For example sg Component src/components/.

Templates are stored in a directory .sg_templates in the project root. Each template has it's own directory. You can use SG syntax in any filenames and inside files with *.sg extensions. (After generation extension will be deleted, so test.js.sg will become just test.js)

SG syntax

SG syntax is very simple:

  1. ##SG:VARIABLENAME##

    This will simply be replaced by the value of the variable during generation.

  2. ##SG:IF(VARIABLENAME)##...##SG:ENDIF(VARIABLENAME)##

    It's simple. If at generation there will be a variable with the same name, the content in the condition will be written to the file. If not ... Well, you understand.

    WARN: No else, no logic. Just simplest if.

And, by the way, variable names are not case sensitive. Like, at all.

Generation from templates

To generate from this template, just enter sg generate YourTemplateName

To pass variable with value use variable_name:variable_value, like sg generate YourTemplateName testvar:helloworld.

To pass variable without value (you should only use it for if, otherwise instead of variable value it will be 'undefined') use variable_name, like sg generate YourTemplateName testvar.