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

package-json-from-template

v0.0.3

Published

Generate a package.json file from a template

Downloads

3

Readme

Package.json From Template Build Status

Generate a package.json file from a template

Why

  • You might find this project useful if you need to generate a node module with different dependencies which uses a different package.json configuration from your repository configuration
  • It saves you time
  • It's DRY

When to use it

Sometimes you create a repository that generates a packaged version of your project and you want that to have it own package.json file but the same name and version inherited from your original project.

Install

If you want to install package-json-from-template globally, use the follow command from your terminal:

$ npm install -g package-json-from-template

Otherwise just add PackageJsonFromTemplate to your project with:

$ npm install --save-dev package-json-from-template

If you prefer using Yarn:

$ yarn add --dev package-json-from-template

Usage

  $ Usage: pack-gen [path] [options] -- [diff args]

  Options
    -t, --template=<filename>   The template file to be used for generating the new package.json file. [default: <path>/package.tpl.json]

    -s, --source=<filename>     The location of your `package.json` file. [default: the root project directory will be used]

  [path]  The working directory in where generating package.json file

  Examples
  Generate a new package.json file inside the ./package folder
  $ pack-gen package

  Generate a new package.json using the base package.json file located under the src directory
  $ pack-gen package --source=src/package.json

  Generate a new package.json file inside the ./package folder using a my-template.json file as a template
  $ pack-gen package --template=my-template.json

Example

Now, assuming that your project generate a distribution version of your node module inside a dist folder, add a pack-gen script to generate a package.json file inside that directory to call after your build task is completed.

"scripts": {
  "pack-gen": "pack-gen ./dist",
}

Note that your dist folder will need to contain a package.tpl.json file to use as a template. If you wish to use a template file sitting elsewhere, you can use the template flag and specify a different path like this:

"scripts": {
  "pack-gen": "pack-gen ./dist --template=/templates/my-package.teplate.json",
}

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Add your changes: git add .
  4. Commit your changes: git commit -am 'Add some feature'
  5. Push to the branch: git push origin my-new-feature
  6. Submit a pull request :sunglasses:

License

MIT License © SonnY