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

kopie

v1.0.7

Published

Simple scaffolding utility using Handlebars for compiling templates. This is used internally, no tests currently it works but use at own risk.

Downloads

1

Readme

Kopie

Simple scaffolding utility using Handlebars for compiling templates. This is used internally, no tests currently it works but use at own risk.

But hey you're only generating templates so probably no big whoop.

Installing

npm install kopie -g

Usage

Use generate, gen or g to generate a template. Generate requires a name, shown below as page and an output path, shown below as output/directory.

In your .kopie/config.json file you can configure your root directory where generators will output to. You can also specify in the generator's config a base sub directory from the above root.

Behind the scenes Kopie does the following join(root, base, output) where output is shown below as output/directory.

ko generate page output/directory --props.key=value

Templates

If you've used Handlebars or really just about any templating engine you should be right at home. Any valid Handlebars or Handlebars-Helpers configuration works.

Consider the following template named demo

<p>Hello my name is {{capitalize name}}</p>

Using command ko g demo demo --props.name='Milton Waddams'

<p>Hello my name is Milton Waddams</p>

You can define required arguments, options and props for your generator. You can also defined defaults. Here's an example below.

Here below dest within required.args ensures that you provide a destination path. Consider this command ko g page components/login. The below config demands components/login be provided or an error will be thrown.

"page": {
  "name": "page",
  "isDirectory": true,
  "action": "default",
  "base": "pages",
  "defaults": {
    "args": [],
    "props": {
      "name": "MyComponent"
    }
  },
  "required": {
    "args": [
      "dest"
    ],
    "props": [
      "name"
    ]
  }
}

Actions

In your ./.kopie/actions folder are the default actions Kopie ships with, see index.js. Your generator config allows you to specify an action to be used to generate your template. Many use cases can be satisfied with the defaultAction action.

You'll notice also an advancedAction method in actions.js. This shows you the workflow of how Kopie handles rendering templates by default.

To create some custom task simple create and export a new generator function that fits the work flow you need.

What's Next

As time permits more examples of more advanced configurations, for features adds etc. Again all about time.