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

battlemake

v0.0.14

Published

Front-end build system with web server and watchers, using jade+browserify+less+webfonts.

Downloads

10

Readme

Battlemake

This is my first use of Gulp, so it's probably terrible.

I created a build system for use with simple projects. It uses Less.js for stylesheets, Jade for templates, and Browserify for JavaScript.

Example usage

var config = {
	/* Names of extra tasks to run during build step */
	extraTasks: [],
	paths: {
		/* Relative path to output directory */
		out: 'out'
	},
	bundles: {
		/* Client javascript bundle and source-map*/
		client: 'client.js',
		clientMap: 'client.json',
		/* Vendor javascript bundle */
		vendor: 'vendor.js',
		/* Stylesheet */
		styles: 'style.css'
	},
	globs: {
		/* Passed to BROWSERIFY entry point(s) */
		js: ['./script.js'],
		/* Glob for LESS entry point(s) */
		less: ['style.less'],
		/* Glob for JADE templates */
		jade: ['pages/*.jade', 'pages/**/*.jade'],
		/* Glob for NPM files to copy to output folder */
		npmAssets: ['./node_modules/**/*.@(png|jpg|jpeg|gif|woff|woff2|eot|ttf|otf|svg)']
	},
	/*
	 * Path to list of Google Webfonts to install
	 * See my battlesnake/gulp-google-webfonts gulp plugin
	 */
	fonts: 'fonts.list',
	/*
	 * Used to generate vendor script bundle - simply globbing in
	 * node_modules would pull in devDependencies too, which we do not want
	 */
	dependencies: require('./package.json').dependencies,
	/*
	 * Dependencies which contain no JavaScript, and thus which shouldn't be
	 * added to the vendor bundle
	 */
	jsFreeDependencies: ['font-awesome'],
	/* Parameters for testing (gulp test) */
	test: {
		/* Port for test HTTP server to listen on */
		port: 1234
	}
};

/* Generate the build system */
var battlemake = require('battlemake')(config);

Modes

live=1 gulp - build files for deployment (takes ages), exit afterwards instead of watching for changes.

gulp where live is empty or zero - build files for testing (no minification, much quicker), start watchers to do incremental rebuilds when files change.

gulp test - As before, but a connect.js web server is also launched from the output directory.