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

normalize-build

v1.1.0

Published

Higher-level builder for Normalize

Downloads

8

Readme

Normalize Build

NPM version

Dependency Status License Downloads Gittip

High level builder for normalize using with normalize-builder and file-watch. The JS API is as close to nlz-build(1)'s API as possible.

  • Automatically includes the require() implementation
  • Automatically executes the entry point - require(boot)
  • Automatically watch for file changes and reuilbd

API

var Build = require('normalize-build')

var builder = Build(options)

builder = Build(options)

Pretty much all the same as the other libraries.

  • directory: 'repositories' - directory to install all the remote dependencies
  • agent - a normalize-agent instance

builder.add(entrypoint, options)

Add an entry point. Must be an absolute URI.

JavaScript options:

  • require: true - include the require() implementation
  • autorequire: true - automatically execute the entry point

builder.watch()

Run as a watcher. The process remains open, and the entry points will automatically rebuild on file changes.

var text = yield* builder.build(entrypoint)

Build a specific entry point. Returns the result as a string.

var results[] = yield* builder.build()

Without an entrypoint, .build() will build all the entry points in the order defined. If you forget, check .entrypoints.

Event: tree

Every time the tree is resolved.

build.on('tree', function (tree, ms) {
  console.log('built tree in: ' + ms + 'ms')
})

Event: <entrypoint>

Every time an entry point is built, an event by its name will be built.

build.on('/User/jong/index.js', function (js) {
  fs.writeFile('/User/jong/build/index.js', js)
})

Note

If you don't use .watch(), you should just use builder.build(), then options.agent.close() to close the connection to the server. Otherwise, the process will never exit.