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

templeme

v0.0.7

Published

A CLI tool to generate code structure templates

Readme

TempleMe

Create your code temples (base and sacred folder and file templates that you need to repeat across the entire project) and share them!

CLI for creating your code temples, base structures that should be repeated across the project

Options:
  -V, --version                                 output the version number
  -h, --help                                    display help for command

Commands:
  init                                          Create a new templeme folder
  create [name]                                 Create a new templeme
  list                                          Lists all available temples
  copy [options] [source] [destination] [name]
  help [command]                                display help for command

See it in action

https://github.com/user-attachments/assets/acd3d850-8617-40c8-af14-a4c1971bedd9

How to install

# For NPM:
npm i templeme -g

# For Yarn:
yarn i templeme -g

# For PNPM:
pnpm i templeme -g

How to use

First, you need to initialize TempleMe with the following command. It will create a .templeme folder at the root of your project.

# Initializes .temples folder in your project
templeme init

After that, you can create your first template by running:

# Create your first temple
templeme create react-component

With you template created, you can edit the files inside .templeme/react-component and add your code structure. Here's a exemple file:

// .templeme/react-component/placeholder-value.component.tsx

export type PlaceholderValueProps = {};

export const PlaceholderValue = (props: PlaceholderValueProps) => (
  <div>Hello from Placeholder Value Component!</div>
);

This means that, when you want to create your component from react-component template, everywhere that TempleMe finds PlaceholderValue, it will replace with your component name, keeping the casing.

So, if you run now:

# Replicate your temples into your project easily
# Anywhere in your file name or contents that TempleMe finds "Placeholder Value", it will replace to "Button", keeping the casing
templeme copy react-component src/components/ui cool-button

You will see that a new file will be created, like this:

// src/components/ui/cool-button.component.tsx

export type CoolButtonProps = {};

export const CoolButton = (props: CoolButtonProps) => (
  <div>Hello from Cool Button Component!</div>
);

You can put as many files inside your Template as you wish :)

Other useful commands are

# Outputs available commands
templeme help

# Outputs command details
templeme help init|create|list|copy

# Outputs to the terminal the new files instead of creating them
templeme copy react-component src/components/ui/button --dry-run

# Copies only the subfolder of your Temple, instead of the entire code
templeme copy react-component src/components/ui/button --f subfolder

# Copies the temple from a Github Repo and Subfolder
templeme copy [email protected]:githubuser/githubrepo.git src/components/ui/button --f subfolder