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

new-file

v1.2.2

Published

Simple file templates.

Downloads

29

Readme

Build Status

Title

Super simple file templates, no fuss, just the way you like them.

Video

Install

npm install -g new-file

.template.yml

Create folders that contain the files that make up your template.

Include a .template.yml file within the folder defining the template and variable parameters to insert into the files:

# .template.yml

name: React Component (TSX)
folder: NAME
install: true # Optionally `{yarn|npm} install` on the folder (default: false).
variables:
  NAME: Component name
  DESCRIPTION: Description
  NAMESPACE: Storybook namespace

The folder NAME is taken as a parameter from the command line. Each variable key (eg NAME, DESCRIPTION, NAMESPACE) is inserted into the files where the variable name is surrunded by double __, eg:

export class __NAME__ extends React.Component<I__NAME__Props> {
  public render() {
    return <div>__NAME__</div>;
  }
}

.templates.yml

Place an index in some containing folder where want the templates to be accessible via the command-line from, eg:

# .templates.yml

templateDirs:
  - code/templates/*/
  - helpers/my-other-templates/*/

package.json

If you are creating a template that contains a package.json file within it, you can use the special __LATEST__ version value for dependencies. The generator will retrieve the latest version of the module from NPM and insert it.

{
  "name": "__NAME__",
  "version": "0.0.0",
  "dependencies": {
    "ramda": "__LATEST__"
  },
  "devDependencies": {
    "electron": "__LATEST__",
  },
}

NOTE: If you are already using LATEST as a variable name, your variable name will override this feature.