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

copywriter

v1.0.1

Published

## Installation

Downloads

5

Readme

Copywriter

Installation

Locally

$ cd [repository root] && npm install --save-dev [email protected]:tonysickpony/copywriter.git

Globally

$ npm install --global [email protected]:tonysickpony/copywriter.git

Command line API

Locally

$ cd [repository root] && ./node_modules/.bin/copywriter -f /path/to/your/config/file.json

Globally

$ copywriter -f /path/to/your/config/file.json

Configuration file

see example config

{
    "vars": {
        "key": "value",
        "key2": "value2"
    },
    "mappings": {
        "inputFile1": "outputFile1",
        "inputFile2": "outputFile2",
        "inputDir": "outputDir"
    },
    "options": {
        "templateExtensions": [
            "tmp",
            "otherTemplateFileFormat"
        ]
    }
}

Precedence

Latter entries will overide former entries. Files will always overide directories.

For example the configuration below:

{
    "vars": {
        "key": "value"
    },
    "mappings": {
        "inputDir": "outputDir",
        "inputDir/subDir": "outputDir2",
        "inputDir/a.tmp": "file.ext"
    },
    "options": {
        "templateExtensions": [
            "tmp"
        ]
    }
}

with a file system structured like this:

└── inputDir
    ├── a.tmp
    ├── b.tmp
    └── subDir
        └── c.tmp

will generate file system structured like this:

├── file.ext
├── outputDir
│   └── b
└── outputDir2
    └── c

Interpolate variables

The templating uses lodash's _.template() function. Template delimiter we choose is handle bar/mustache style {{ variable }} and this is hardcoded for the moment.

So the template file may look like:

my keys:
    - {{ key }}
    - {{ key2 }}

System Environment Variables

The system envs can be picked up using $ENV.envname style value. For instance to get the home directory you should write the variable like "myHOmeDir": "$ENV.home".

Uninstallation

Locally

$ cd [repository root] && npm rm --save-dev copywriter

Globally

$ npm rm --global copywriter

Development

Prerequisite

Download repository

$ git clone git://[email protected]:gorapid/rapid-template.git && cd rapid-template

Install dependencies

$ npm install

Or if you have yarn installed

$ yarn install

Run tests. We choose ava as our test suite

$ npm test

Test coverage. We choose nyc as our test coverage tool

$ npm run coverage

Code style linting. We choose js standard as our code standard and linting tool

$ npm run lint

Bugs and feature requests