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

mechanism

v0.0.14

Published

Minimalistic build system

Downloads

11

Readme

Mechanism Build Status Dependency Status

A minimalistic build system that operates files and tasks. It constructs a graph of build dependencies, marks nodes to be rebuilt, and executes the graph concurrently.

Usage

var Mechanism = require('mechanism');
var msm = new Mechanism();

var concat = require('mechanism-concat');
var concat10 = concat({ delimiter: '\n' });
var closure = require('mechanism-closure-compiler');
var imagemin = require('mechanism-imagemin');

var paths = {
  scripts: ['client/js/**/*.js', '!client/external/**/*.js'],
  images: 'client/img/**/*'
};

var outs = {
  scripts: {
    concat: 'temp/scripts.concat',
    closure: 'temp/scripts.closure'
  }
};

msm.operate(
  // out of files
  paths.scripts,
  // make file
  outs.scripts.concat,
  // using plugin
  concat10
);

msm.operate(
  outs.scripts.concat,
  outs.scripts.closure,
  closure({
    compilerPath: "../path/to/compiler.jar",
    compilerFlags: {
      compilation_level: "ADVANCED_OPTIMIZATIONS"
    }
  })
);

msm.on("finish", function() {
  console.log("finish");
});

msm.on("error", function(error) {
  console.log(error);
});

msm.start();

Intermediate Files

You are supposed to name intermediate files instead of naming tasks. One operate task is described by it's source and target files. Tasks connect each other using the files names.

Chaining operations

You can use targets from previous operation as sources in next operation. Use operate again.

msm.operate(

  paths.scripts,
  outs.scripts.concat,
  concat10

).operate(

  outs.scripts.closure,
  closure({
    compilerPath: "../path/to/compiler.jar",
    compilerFlags: {
      compilation_level: "ADVANCED_OPTIMIZATIONS"
    }
  })

);

Build API

Plugin API

Incremental Builds

Just rerun start() periodically. Mechanism calculates what files are on-disk files (excluding intermediate files), and handles it's own cache of on-disk files and their state.