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

templated-npm

v1.4.0

Published

Automatically copy common files or part of files between projects

Downloads

2

Readme

Templated

You can copy/link automatically all your common config files of all your projects from a template directory. You can config to copy parts of files that is common in different projects. It's util for common config files/parts for all subprojects/microservices like .gitignore, copyright, etc.

Config your project

Add the dependency:

npm install templated-npm --save-dependency

You must create a "templated.json" file with your templated reposiotory source configured:

{
    "source": "../templated-example-template2"
}

Or you can indicate multiple sources with an array:

{
    "sources": [         
        "../templated-example-template"
        "../templated-example-template2"
    ]
}

Config your template repository

Copy files

All files in the templated repository was copied to your project automatically.

Copy parts

If you want to embed a part of file you can create in your templated repository a file with the name: file-name-when-you-want-embed|embed-tag.part

For example:

readme.md|copyright.part

The "content part" was replaced in your file with the position of the embed-tag indicated. You must indicate in your file where you want put the content with your embed tag. In a .md/.html file it is with:

<!-- start|embed-tag --> it was replaced <!-- end|embed-tag -->

For example:

<!-- start|copyright --> it was replaced <!-- end|copyright -->

If you want put in de start or de end of the file you don't need define the embed tag position. Simply use files with tag "start" or "end" like:

readme.md|start.part

readme.md|end.part

You can view an example of use in: https://github.com/miyoda/templated-example-usage.git

The example use the template: https://github.com/miyoda/templated-example-template.git