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

@universal-packages/template-populator

v1.0.19

Published

Simple template transferring replacing templated contents

Downloads

11,518

Readme

Template Populator

npm version Testing codecov

For that well known thing that some libraries do to initialize a project by populating a directory with a boilerplate of files with your project name all over the place, that what this does, exactly the part where the template files are transferred and processed.

Install

npm install @universal-packages/template-populator

Global methods

populateTemplates(fromLocation: string, toLocation: string, [options])

Reads deeply into a template directory structure and reconstructs it in another location processing the template files

import { populateTemplates } from '@universal-packages/template-populator'

async function test() {
  await populateTemplates('./templates', 'project/directory')
}

test()

Lets say ./templates looks like this in disk:

templates
  |- app
    |- App.js.template
    |- models
      |- User.js.template
  |- config
    |- db.json.template
    |- secrets
      |- api.yaml.template

We will end up with something like

project/directory
  |- app
    |- App.js
    |- models
      |- User.js
  |- config
    |- db.json
    |- secrets
      |- api.yaml

Options

  • override boolean If the file already exists in the destination location, should it be override or should it be let alone

  • replacementVariables string[] Provide variables to be replaced in the template files with the format {{ variable }}

    export class {{ className }} extends {{ classExtension }} {
      ...
    }
  • templateExtension string By default .template files are going to be the ones being mapped, but you can change which extension should be used.

transferTemplateFile(fromLocation: string, toLocation: string, [options])

Reads the specified template file replace any variables in it and save it to the destination location. So basically handles just one file.

import { transferTemplateFile } from '@universal-packages/template-populator'

async function test() {
  await transferTemplateFile('./templates/App.js.template', 'project/directory/App.js')
}

Options

  • override boolean If the file already exists in the destination location, should i be override or should it be let alone

  • replacementVariables string[] Provide variables to be replaced in the template files with the format {{ variable }}

    export class {{ className }} extends {{ classExtension }} {
      ...
    }

Typescript

This library is developed in TypeScript and shipped fully typed.

Contributing

The development of this library happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving this library.

License

MIT licensed.