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

bepacked

v0.0.2

Published

Pack external assets into your html

Downloads

133

Readme

bepacked Build Status

Pack external assets into your html.

Bepacked came into being as a helper for bedecked, allowing you to inline static assets and create standalone presentations that could be run without an internet connection. In general it can be used to inline (most) assets for any local or remote HTML document.

Usage

Bepacked exports a single function:

var bepacked = require('bepacked');

/**
 * Bepacked can take in a chunk of html, a path to a local html file, or a url.
 */
var input = '<html>...</html>';

/**
 * Bepacked is configurable, tell it exactly which types of assets you'd like to
 * inline. this is an optional argument and by default we'll inline everything
 * we can.
 *
 * The options hash can also specify a current working directory. This is useful
 * for example when you pass bepacked a bunch of HTML with relative asset paths,
 * we'll use cwd to resolve those assets. This defaults to the current working
 * directoy when unless the input was actually a file or url in which case that
 * file's directly is used.
 */
var opts = {
  cwd: process.cwd(),
  scripts: true,
  styles: true,
  images: true
};

/**
 * You may optionally pass a callback as the final parameter. It will be given
 * an error if there was one and the packed html.
 */
var cb = function(error, packedHtml) {
  // ...
};

/**
 * Bepacked also returns a promise if you're not into the whole callback thing.
 */
var promise = bepacked(input, opts, cb);

License

MIT