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

@ruben__nijhuis/motive

v1.0.1

Published

A simple template generator

Readme

Motive

Quickly generate files using an easy to use command line application. Select one of your templates, answer the questions and in no time the files will be generated.

How to configure your template

Two things are important.

The file name and the file name in the option.json match! There are no missing properties (names in the template or in the options.json) I haven't fully configured error/file checking

An example of an options.json file

{
    // These will be set for all files
	"general": {
		"name": "What is the name of the class?"
	},
    // Index of all files (might turn this into an array)
	"files": {
		"CPP_CLASS_CPP": {
            // Config regarding the file name output
			"config": {
                "fileName": "name",
				"extension": ".cpp"
			}
		},
		"CPP_CLASS_HPP": {
            // Additional info that might be needed per file
			"values": {
				"name_upppercase": "What is the class name in uppercase?"
			},
			"config": {
                "fileName": "name",
				"extension": ".hpp"
			}
		}
	}
}

An example of a template file

#include "{{name}}.hpp"

{{name}}::{{name}}(void)
{
    std::cout << "{{name}} created with an empty construcor" << std::endl;

    this->_type = "{{name}}";

    return;
}

{{name}}::~{{name}}(void)
{
    std::cout << "{{name}} " << this->_type << " deconstructed" << std::endl;
    return;
}

{{name}}::{{name}}(const {{name}}& other)
{
    std::cout << "{{name}} created by copy" << std::endl;
    *this = other;
    return;
}

{{name}}& {{name}}::operator=(const {{name}}& other)
{
    std::cout << "{{name}} created by assertion" << std::endl;

    if (this != &other)
    {
        this->_type = other._type;
    }

    return (*this);
}

The output is created using MustacheJS