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

essential-bundle

v0.9.1

Published

Transform resources in your Web Component into a deliverable bundle. Use `names.json`, `bower.json` or `package.json` to define where your resources and assets are. Identify JS, CSS, images, fonts, views and templates.

Downloads

14

Readme

essential-bundles

Transform resources in your Web Component into a deliverable bundle. Use names.json, bower.json or package.json to define where your resources and assets are. Identify JS, CSS, images, fonts, views and templates.

With Browserify and SocketStream can access your bundle and serve it to the browser.

You can use modules of your own in combination with some added using bower.

build status

Installation

Installation is via npm:

$ npm install essential-bundle

NPM

How to use.

By default directories in your project are supported as modules. So you can add,

users
+ js/
+ images/
+ fonts/
+ css/
+ views/
+ templates/
+ users.js
+ names.json

Your users.js file would require the submodules inside js/.

var uuid = require('uuid');
exports.account = require('./js/account');
exports.profile = require('./js/profile');

Make sure you fill in main in names.json (or bower.json/package.json) to be users.js.

Add a where section to names.json.

{
	"name":"users",
	"main":"users.js",
	"where": {
		"js": "js/**/*.js",
		"css": "css/**/*.less",
		"views": "views/**/*.html",
		"templates": "templates/**/*.html",
		"assets": ["fonts","images"]
	}
}

In your application you can pull in the users code with require("users"). It will resolve to a module with a combination of js, views, templates.

Gulp

The simplest way to use this in Gulp is with the browserify like call.

var gulpBundler = require('essential-bundle').gulp;
gulpBundler({
	outputName: 'body.js',
	entries: ['./client/code/site/body.js'], // must start with dot to be relative to cwd
	debug: true // source maps
	})
    .pipe(gulp.dest(destDir));

Browserify

browserify({
  transforms: ['essential-bundle/browserify-transform']
});
var essentialTransform = require('essential-bundle').browserifyTransform({
	sources: ['app','common']
});
browserify({
  transforms: [essentialTransform]
});

Grunt Browserify

TODO

Socketstream

TODO

Notes

This is based on great work from debowerify by Eugene Ware