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

@fletchers-tools/projenerator

v2.0.2

Published

Template-based boilerplate code generator

Readme

Projenerator

Template-based boilerplate code generator

1. Create a config file

Create a .projenerator directory inside your project and add a projenerator config file.

.projenerator/config.json

{
  "targetDir": "../src",
}

2. Add templates

Add handlebars templates inside .projenerator/templates directory

You can use handlebars templates syntax inside both directories/files names and it's content

You will have entityName and entityNamePlural variables available in your template's context, but avoid using them as they are, ensure they have a proper casing by combining them with case-transform helpers: camel, pascal, kebab, snake, upper-snake and upper

{{entityName}}
{{entityNamePlural}}

{{camel entityName}} // entityName
{{pascal entityName}} // EntityName
{{kebab entityName}} // entity-name
{{snake entityName}} // entity_name

{{upper (snake entityName)}} // ENTITY_NAME
{{upper-snake entityName}} // ENTITY_NAME

Example .projenerator directory structure:

.projenerator
    - config.json
    - templates
        - component
            - {{pascal entityName}}
                - {{camel entityName}}.module.scss.hbs
                - {{pascal entityName}}.tsx.hbs
                - index.ts.hbs
            - {{pascal entityName}}--extended // --variant=extended
                - {{camel entityName}}.module.scss.hbs
                - {{pascal entityName}}Context.tsx.hbs
                - {{pascal entityName}}.tsx.hbs
                - index.ts.hbs
        - helper
          - {{camel entityName}}.helper.ts.hbs

3. Generate code

Use make command to generate a boilerplate code

# projenerator make entity-type entity-name
projenerator make component test-component

Pass additional options to have more control over the generation process

projenerator make component person --plural=people --variant=extended --scope=features/user

Make command structure:

projenerator make
    <entity-type> // Entity type
    <entity-name> // Entity name
    -p, --plural <plural> // Entity plural name
    -v, --variant <variant> // Variant modifier
    -s, --scope <scope> // Scope modifier (pass relative target path for a generated enitity)