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

license-stamper

v1.0.2

Published

stamp a license text from a file at the top each file in your repo in appropriate comment section

Downloads

6

Readme

license-stamper

stamps a license text from a file (see sample/template.mustache) at the top of each file in the input directory using appropriate comments section (as defined in comment_block.yaml) and writes the file to the specified output directory (or input directory if output directory not specified)

It also ensures that it does not add the same license text again if already existing.

Usage

npm start

Or

npm i license-stamper --save-dev

and

node -e 'require(`license-stamper`).run()' '.'

or use the following in your pre publish pipeline

require('license-stamper').run(inputDir, outputDir, configYamlPath, templatePath)

Contributions

Any type of contribution towards enhancing this is welcomed

ToDos

  • '#!/usr/bin/env' node should remain as first line
  • Remove old license and update if config changed