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

packify

v1.1.2

Published

packs up browserify apps by inlining all assets into one html file

Downloads

10

Readme

packify

packs up browserify apps by inlining all assets into one html file

npm install packify -g
packify index.html > packed.html

dat

how it works

packify will do the following transformations:

  • <img src="foo.png"> -> <img src="data:...">
  • <link rel="stylesheet" href="foo.css"> -> <style> /** styles here **/ </style>
  • <script src="foo.js"> -> <script> /** browserified foo.js here **/ </script>
  • background-image { url(foo.png) } -> background-image { url('data:...') }

all transformations are handled by dependencies: inline-images, inline-styles, imageinliner and scriptify

notes:

  • url(foo.png) inside stylesheets will also get converted to inline data-uris
  • only relative URIs will be transformed, e.g. <script src="http://foo.com/foo.js"> will be ignored

example

the dat-editor module/application uses this.

before packify: https://github.com/maxogden/dat-editor/blob/master/index.html after packify: https://github.com/maxogden/dat-editor/blob/master/prebuilt.html

prebuilt.html is generated by this npm command https://github.com/maxogden/dat-editor/blob/master/package.json#L8 (note the brfs transform https://github.com/maxogden/dat-editor/blob/master/package.json#L28-L32)

usage

javascript

var packify = require('packify')

var opts = {
  html: "<html> ... your html here... </html>",
  args: ['arguments', 'for', 'browserify'],
  selector: 'script' // css selector passed to scriptify for it to select elements to browserify
}

packify(opts, function(err, packed) {
  console.log(packed.toString())
})

CLI

packify <path-to-html-file>

when using on the CLI any additional arguments beyond the HTML file will be passed straight to browserify, e.g.

packify index.html -t brfs

will run browserify like browserify -t brfs