monolithed

const fs = require('fs'),
	dirsum = require('dirsum')
;

module.exports = function (grunt) {
	grunt.registerMultiTask('hash', 'Hash-sum file.', function () {
		const done = this.async();

		var options = this.options({
			algorithm: 'md5'

monolithed

vi file.js
:%!xxd

monolithed

'use strict';

var utils = require('util');

module.exports = function (grunt, options) {
	return {
		index: {
			options: {
				template: function (data) {
					var content = utils.format('return %s(%j);', data.contents, {

monolithed

'use strict';

import FastClick from 'FastClick';


var utils = {
	parse_events (events) {
		return events.split(/[\s,]+/);
	}
};

monolithed

/*!
 * tasks/fest
 */

'use strict';

var utils = require('util');

module.exports = function (grunt, options) {
	return {

monolithed

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

monolithed

/**
 * utils/sync
 */

'use strict';

var fs    = require('fs'),
	grunt = require('grunt'),
	path  = require('path');

monolithed

'use strict';

/**
 * @class DOMEvent
 * @param {Object} element
 */
export default class DOMEvent {
	constructor (element) {
		this.element = element;
		this.events = {};

monolithed

scroll-behavior: smooth;
will-change: none;

monolithed

'use strict';


/**
 * @class
 * @param {number} size
 */
export default class FixedList {
	constructor (size) {