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

extend-package-scripts-example

v1.0.3

Published

An example of how to extend your package.json scripts by passing extra files or flags as arguments.

Downloads

8

Readme

extend-package-scripts-example

An example of how to extend your package.json scripts by passing extra files or flags as arguments.

Install

git clone [email protected]:yamafaktory/extend-package-scripts-example.git

npm i

Why

  1. npm is an amazing package manager and an efficient build tool / task runner too.

  2. You do not need to install / wrap your mind around / configure another bloated tool to get the stuff done.

  3. You like Unix and so does npm.

How

Please first take a look at the package.json file.

"config": {
  "file": "example.es6"
},
"scripts": {
  "compile": "babel --presets es2015 $npm_package_config_file",
  "compile:file": "npm run-script compile -- -o file.js",
  "compile:watch": "npm run-script compile -- -w -o file.js"
}

You will notice that:

  • You can create your own variables in the config section.

  • You can reuse these variables in the script section (e.g. $npm_package_config_whatever).

  • You can create extended tasks on purpose by appending -- plus new arguments to one given initial task.

Play with the example

The provided example is based on the Babel compiler.

The main task display a simple es2015-to-es5 JavaScript transpiled file to the stdout:

npm run compile

The same task is extended in order to write it to a file:

npm run compile:file

And then extended again to create a watcher:

npm run compile:watch

Is that new?

Absolutely not.

Please read the documentation.

Bonus

What if I want to overwrite the file variable of the config section?

npm config set extend-package-scripts-example:file another-file.es6 && npm run compile:file

And you can do a lot more!

Licence

MIT © Davy Duperron