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

project-template

v1.1.1

Published

Generate a project based on a directory of template files and corresponding template values

Downloads

24

Readme

project-template

npm version

Generate a project based on a directory of template files and corresponding template values.

Requirements

  • Node JS v6+

Install

yarn add project-template

Example

yarn run example

See example/index.js

Usage

const projectTemplate = require('project-template');

projectTemplate({
  templatePath: '/path/to/templates',
  buildPath: '/path/to/build',
  params: {
    'path/to/file.txt': {
      firstParam: 'First param value',
      secondParam: 'Second param value',
    },
    'path/to/different/file.txt': {
      anotherParam: 'Another param value',
    },
  },
})
.then(files => console.log('Done', files))
.catch(err => console.error('Error', err));

Things to keep in mind

  • Template files are expected to use ect syntax
  • Directory structure of files in templatePath is maintained in buildPath
  • All files in templatePath with fileExtension must be included in params
  • Files in templatePath without fileExtension are just copied over to buildPath
  • You cannot have two files with the same file path where one has fileExtension and the other doesn't

API

projectTemplate(options) -> Promise<Array<String>>

options

| Key | Type | Required | Default | Notes | | --- | --- | --- | --- | --- | | templatePath | String | Yes | | Directory path containing template files | | buildPath | String | Yes | | Directory path to write generated files to | | params | Object | No | {} | Keys are relative paths of template files (with fileExtension stripped). Values are objects of template variables | | ignoreFiles | Array<String> | No | [] | File paths to ignore (exclude the fileExtension for template files). Useful for ect partials | | fileExtension | String | No | ect | File extension of template files |

Result

The promise is resolved with an array of file paths of generated files, relative to the buildPath directory.