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

diy-build

v1.0.9

Published

do it yourself - build DSL

Downloads

24

Readme

diy NPM version

do it yourself - build DSL

install

npm install diy-build

example

concatenate and minify javascript files

Assume you have two files (src/file1.js and src/file2.js) that you want to concatenate and minify into a single _site/client.js file. Here's how you'd write a DIY (ES6) program for the task at hand:

diy source file

/* configure.js */

var {
  generateProject
} = require("diy-build");

generateProject(_ => {
  _.collect("all", _ => {
    _.toFile( "_site/client.js", _ => {
      _.minify( _ => {
        _.concat( _ => {
          _.glob("src/*.js")
        })
      })
    })
  })
})

description

DIY uses a top-down approach in which you decompose the construction of each product/target into simpler steps.

Everything begins with the generateProject library function. This function generates the makefile by following the steps indicated in the closure passed as a parameter.

generateProject(_ => {
  _.collect("all",
    ...

This will declare a new Make target (all) associated with the construction of a set of products specified in the closure passed to collect (think of it as a Grunt task).

You could even have a sequence of _.collect to declare multiple targets or even multiple targets nested inside another (to specify nested dependencies):

generateProject(_ => {
  _.collectSeq("all", _ => {
    _.collect("build", _ => {
      /* specify how to build files */
    })
    _.collect("deploy", _ => {
      /* specify how to deploy files */
    }
  })
})

Let's go back to our example. The _.collect operation specifies the files that must be built:

_.collect("all", _ => {
  _.toFile( "_site/client.js", _ => {
    ...

Here, we are specifying that the all target corresponds to the construction of the file _site/client.js. In this case, _.toFile receives a closure that constructs the minified concatenation of all src/*.js:

_.toFile( "_site/client.js", _ => {
  _.minify( _ => {
    _.concat( _ => {
      _.glob("src/*.js")
      ...

Check out the docs for additional ways to process files

makefile generation

To generate the makefile we use babel to get ES5:

babel configure.js | node

And here's the generated makefile.

The makefile comes with two default targets (prepare and clean) and all the targets defined with collect:

> make prepare      # Creates destination directories
> make clean        # Removes all products
> make all          # Execute commands associated with `all`

Make provides a way to specify the maximum parallelism to be used for building targets:

> make all -j 8     # Build all, execute up to 8 concurrent commands.

customization

What about your favorite CSS/JS preprocessor and other minifiers?

Here's how you would define a new processing step to compile Javascript with a bunch of Browserify plugins:

_.browserify = (src, ...deps) => {
  var command = (_) => `./node_modules/.bin/browserify -t liveify -t node-lessify  ${_.source} -o ${_.product}`
  var product = (_) => `${_.source.replace(/\..*/, '.bfd.js')}`
  _.compileFiles(...([ command, product, src ].concat(deps)))
}

_.compileFiles is a built-in function that allows you to easily construct new processing steps. Its first two parameters are two templates:

  1. A function to build the command line; and
  2. A function to build the product name.

The remaining parameters are src (glob for the source files) and the source dependencies.

generateProject(_ => {

  _.browserify = (dir, ...deps) => {
    var command = (_) => `./node_modules/.bin/browserify -t liveify -t node-lessify  ${_.source} -o ${_.product}`
    var product = (_) => `${_.source.replace(/\..*/, '.bfd.js')}`
    _.compileFiles(...([ command, product, dir ].concat(deps)))
  }

  _.collect("all", _ => {
    _.toFile( "_site/client.js", _ => {
        _.browserify("src/index.ls", "src/**/*.less", "src/**/*.ls")
    })
  })
}

serving and livereloading

Serving static files from a directory and livereloading upon a change of a product are supported through pm2 and tiny-lr. We can create two make targets (start and stop) that start and stop both services:

generateProject(_ => {

    /* ... */

  _.collect("start", _ => {
    _.startWatch("_site/**/*")
    _.startServe("_site")
  })

  _.collect("stop", _ => {
    _.stopWatch()
    _.stopServe()
  })

    /* ... */
})

_.startWatch(glob) is a built-in step that launches a tiny-lr instance to trigger a reload upon a change in files matching the glob. _.startServe(root,port) serves files from the specified root and port.

Author

Vittorio Zaccaria

License

Copyright (c) 2015 Vittorio Zaccaria
Released under the license


This file was generated by verb-cli on March 10, 2015.