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

tempter

v1.0.3

Published

Your own sub-generator. In minutes. Bundled with your project.

Downloads

4

Readme

Your own sub-generator. In minutes. Bundled with your project.

Features

Usage

1. Add tempter to your dev dependencies

yarn add -D tempter
# OR
npm install -dev tempter

Q: Why not CLI?
A: You can bundle it with your boilerplate this way!

2. Create your generator file (e.g. generator.js)

// generator.js contents
require('tempter')('your/template/directory')

3. Add your templates to this directory

4. Done! You can now use your generator!

node generator.js

Tip: You may also add it to your npm scripts!

Docs

How to create a template

1. Create a folder (e.g. React Component) for your template in your template directory (e.g. templates)

2. Create a config file template.json for your template

Documentation

3. Add files

Just add template files in the same directory as template.json.

Placeholder documentation

Template configuration

{
  "dir": "src/components",
  "type": "subfolder"
}

| Option | Description | Required | | ------ | ------------------------------------------------------------------------------------------------------- | -------- | | dir | Says where our template should be coppied to | true | | type | Determines if the template should be placed in a subfolder ("subfolder"), or just spread in dir ("spread") | true |

Placeholders

Placeholders may be used in both filenames and the actual templates, they will be replaced by the generator.

| Placeholder | Replaced by | Example | | ----------- | ---------------------------- | ------- | | lowNAME | Name from input, lowercased | name | | uppNAME | Name from input, uppercased | NAME | | capNAME | Name from input, capitalized | Name |

Author

👤 DEVICARUS