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

module-smith

v0.3.1

Published

Build Bot for Node JS

Downloads

10

Readme

Module Smith

A simple extensible npm build bot that works on Linux, SmartOS, and Windows.

Example

Given a small script for building a specific module:

var assert = require('assert'),
    tmp = require('tmp'),
    ModuleSmith = require('module-smith');

var buildbot = ModuleSmith.createModuleSmith();

//
// Grab a temporary directory to build in
//
tmp.dir(function (err, tmpdir) {
  assert.ifError(err);
  //
  // Start our build
  //
  buildbot.build({
    repository: {
      type: 'git',
      url: '[email protected]:bmeck/bcrypt-example.git'
    },
    directories: {
      root: tmpdir
    }
  }, function (err, stream) {
    assert.ifError(err);
    //
    // Pipe out the data to stdio
    //
    stream.pipe(process.stdout);
  });
});

We can dump it to a file via:

node build.js > built.tgz

API

ModuleSmith.createModuleSmith(options)

  • Array options.versions: List of the versions supported with absolute version numbers like ie. '0.8.12'
  • BuildDescription options.defaults: The defaults for a build run using this ModuleSmith.

ModuleSmith.build(buildDescription, callback(err, tgzStream))

Runs a build

BuildDescription

{
  uid: 'nobody',
  gid: 'nobody',
  command: 'install',
  env: {
    'npm_config_registry': 'http://registry.npmjs.org',
    'npm_config_nodedir':  path.join(process.env.HOME, '.node-gyp')
  },
  repository: {
    type: 'git',
    url: '[email protected]:bmeck/bcrypt-example.git'
  },
  directories: {
    root: '/path/to/build/output/root'
  }
}

A build description enumerates a number of values

BuildDescription.command

The npm command that you wish to execute for the build. Can be:

  • install: Installs all module dependencies.
  • build: Runs node-gyp to build any binary dependencies.

BuildDescription.env

Optional environmental variables to spawn npm with.

Some interesting fields are:

  • npm_config_registry - registry to download from
  • npm_config_nodedir - location of node-gyp's include directory

BuildDescription.uid = 'nobody'

Optional user to spawn npm as.

BuildDescription.gid = undefined

Optional group to spawn npm under.

BuildDescription.package

Optional package.json overrides. Can be extended easily from the repository during npm.configure.

Some interesting fields are:

  • engines.node - version to spawn as

BuildDescription.repository

A checkout npm module repository to download before building.

BuildDescription.directories.root

The place to use for creating the build.

Understudy Actions

Extensibility for complex actions can be done via Understudy based actions, only before actions are supported.

  • build.configure (buildDescription)
  • npm.configure (buildDescription)
  • npm.package (buildDescription, package)
  • build.output (buildDescription, tgzStream)

Events

Notifications of actions that have been completed are available via the EventEmitter APIs.

  • npm.spawned (buildDescription, npmProcess)

Hammer Icon by Edward Boatman from The Noun Project