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

parallel-transpile

v0.6.0

Published

Transpile files in parallel using all available CPUs

Downloads

35

Readme

Parallel Transpile

Build Status

This npm module uses webpack loaders and all your CPUs to transpile source as quick as it can.

Installation

npm install -g parallel-transpile

Also install any webpack loaders you require, e.g.

npm install -g cjsx-loader coffee-loader jsx-loader json-loader

Usage

Usage: parallel-transpile [options] -o outputDirectory inputDirectory

  -h, --help          display this help message
  -v, --version       output version number
  -w, --watch         watch input directories for changes
  -o, --output        the output directory
  -p, --parallel      how many instances to run in parallel
                        (defaults to number of CPUs)
  -t, --type          add a type to be converted, see below
                        (can be called multiple times)
  -n, --newer         only build files newer than destination files

Types

  Each type takes an input filter (file extension), a list of loaders, and
  an output extension. To copy a file verbatim, only the input filter is
  required.

  For example, to copy all JSON files verbatim:

    -t ".json"

  To compile a CJSX file to JavaScript:

    -t ".cjsx:coffee-loader,cjsx-loader:.js"

  Loaders operate from right to left, like in webpack.

Example

The following example recurses through the src folder, converting all .cjsx, .coffee and .litcoffee files to .js and copying all .js and .json files verbatim into the build directory. It also watches for changes in src (including additions), updating the build directory as required.

parallel-transpile \
  -o build \
  -w \
  -t .cjsx:jsx-loader,coffee-loader,cjsx-loader:.js \
  -t .coffee:coffee-loader:.js \
  -t .litcoffee:coffee-loader?literate:.js \
  -t .json \
  -t .js \
  src

Usage as a module

You can also use parallel-transpile as a module, which can be useful e.g. in grunt. For a simple parallel build you might do something like:

var parallelTranspile = require('parallel-transpile');

grunt.registerTask("parallel-transpile", function() {
  var done = this.async();
  var options = {
    output: "build",
    source: "src",

    type: [
      ".cjsx:jsx-loader,coffee-loader,cjsx-loader:.js",
      ".coffee:coffee-loader:.js",
      ".litcoffee:coffee-loader?literate:.js",
      ".json",
      ".js"
    ]
  };

  parallelTranspile(options, done);
});

The real power comes when you combine this with watching for changes. You can have your grunt task wait for the initial build to complete before moving on to the next grunt task but continue watching for changes in the background, like this:

var parallelTranspile = require('parallel-transpile');

grunt.registerTask("parallel-transpile:watch", function() {
  var done = this.async();
  var options = {
    output: "build",
    source: "src",

    type: [
      ".cjsx:jsx-loader,coffee-loader,cjsx-loader:.js",
      ".coffee:coffee-loader:.js",
      ".litcoffee:coffee-loader?literate:.js",
      ".json",
      ".js"
    ],

    watch: true,
    initialBuildComplete: done
  };

  parallelTranspile(options, function() {
    console.error("Parallel-transpile exited");
  });
});

License

MIT