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

rush-init-project-plugin

v0.11.1

Published

Rush plugin for initialize project in monorepo

Downloads

65,265

Readme

rush-init-project-plugin

Initialize project in Rush.js monorepo like a pro!

Prerequisite

Rush.js >= 5.57.0

Quick Start

  1. Enabling this rush plugin

Please follow the official doc to enable this plugin in your repo.

  1. Adding your first template

Let's say you want to add a new template named my-template, put the template files under common/_templates/my-template folder.

common/_templates
└── my-template
    ├── README.md
    └── package.json

Now, run rush init-project prompts you select a template list, which contains my-template.

After you answer some simple questions, files under common/_templates/my-template will be added into your project folder, and project configuration will be added to rush.json as well.

Advance Usage

Kind of boring in a template way?

You can create a configuration file to extend initialization process.

See HERE for detail.

Tech Notes

The whole CLI is based on node-plop

All directories under common/_templates/<template_name> are template source code, except those who prefixes with _. For instance, folder named _plugins is treated as internal folder not template folder where you can store shared code across templates.

All source code will be rendered by handlebars, while using custom render engine is supported.

Plenty of handlebar helpers are provided as default by handlebars-helpers

Third party node modules can be used in init.config configuration file by installing them into the corresponding autoinstaller folder, such as common/autoinstallers/rush-plugins/.

Default prompts includes:

  • packageName: "name" field in package.json
  • unscopedPackageName: packageName without npm scope
  • projectFolder: the dest file path where the template will be rendered
  • description: project description
  • authorName: author name