Bondifrench

browserify for webpack users

There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.

Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.

I think that longer-term, separability has more benefits from a maintenance and

Bondifrench

'use strict';

function noop(){}

var contentView = noop;
var elPos = { left: 0, bottom: 0};

var tooltip = {
  show: function(content, options) {
    return function(event) {

Bondifrench

// m.prop is a great pattern, but Plain-old JavaScript Objects (POJO) are
// much more pleasant to work with.
// Here's an example of using POJOs with one- and two-way data binding.

// First, the helper methods
m.setValue = function (obj, prop) {
  return m.withAttr('value', function(value) { obj[prop] = value })
}

Bondifrench

const m = require('mithril')

const stated = hook => vnode => vnode.state[hook](vnode)

const oninit = Comp => vnode => {
  vnode.state.oncreate = m.prop()
  vnode.state.onremove = m.prop()
  vnode.state.view = Comp(vnode)
}

Bondifrench

function multi(){
	var handlers = Array.prototype.filter.call( arguments, function( x ){
		return x instanceof Function 
	} )
	
	return function handle(){
		for( var i = 0; i < handlers.length; i++ )
			handlers[ i ].apply( this, arguments )
	}
}

Bondifrench

function auth(component) {

    return {
        controller: function () {
            var ctrl = this;
            function success(user) {
                Account.user(user)
                ctrl.output = new component.controller()

                m.redraw(true)