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

glov-build-browserify

v1.0.8

Published

Browserify task processor for glov-build

Downloads

20

Readme

Browserify task processor for glov-build

Efficient caching and run-time dynamic reprocessing of bundles with browserify.

API usage:

const browserify = require('glov-build-browserify');


gb.task({
  name: ...,
  ...browserify(options),
});

Options

  • entrypoint - Required. The main/entrypoint file to start bundling. This is passed to browserify as the first argument, after resolving to an on-disk path
  • source - Optional source bucket to find the entrypoint and other dependencies. Default: "source"
  • out - Optional output file. Default: entrypoint.replace('.js', '.bundle.js')
  • sourcemap - Specify false if you are crazy and do not want sourcemaps loaded and generated. Default: true
  • browserify - Arbitrary options to pass to browserify. Default: {}
  • post_bundle_cb - Optional function to run on the bundled source code (as a Buffer) before outputting. Allows injecting build timestamps or similar things. Note that for anything more complicated than character replacement, this is not modifying sourcemaps, so your sourcemaps may become invalid. For those cases, prefer a separate task that takes the output from this task.

Example usage:


// In this example, we *first* pass our source files through `babel`, and
// then bundle them in browserify.  This is _orders of magnitude_ more efficient
// than using babel as a transform in browserify's pipeline, because babel
// (which is very slow) only ever gets run on each source file once per change,
// even between restarts of your build pipeline.

const babel = require('glov-build-babel');
gb.task({
  name: 'babel',
  input: '*.js',
  ...babel(),
});

const glov_build_browserify = require('glov-build-browserify');
gb.task({
  name: 'bundle',
  target: 'dev',
  ...glov_build_browserify({
    entrypoint: 'client/main.js',
    source: 'babel',
    out: 'main.bundle.js',
    browserify: {
      transform: [],
      bundleExternal: false,
    },
    post_bundle_cb: (buf) => {
      // This super inefficient, don't do it like this, modifying the Buffer
      //   in-place is way better!
      return Buffer.from(buf.toString().replace('BUILD_TIMESTAMP', `"${Date.now()}"`));
    },
  }),
});