Debugging Node.js in Chrome DevTools… I never knew!

I’ve been away for node for well what seems like forever, but its maybe been 6 months since I did it at work and 13 months since I did it at home… A long time.

I’ve spent this evening bringing the new Norseman Old Mayfield site that I had been working on before the fall (of mayfield)

Its a promise hell in this project so I thought, urgh somebody must have done something cool by now, google it bosh:


devtool we love you!!!
devtool we love you!!!

Now I can interact with my objects and what not in the f’in mother fudging CONSOLE! hahah yes!

Reasons why I bloody love Browserify!!!

  1. A single sexy file
  2. I can use watchify on it
  3. I am uglifyify the bloody shit out of it!!! 1.7mb file? No a 243kb file.
  4. I can pipe whatever the hell I want to it… (just the things already mentioned, for now anyway)
  5. I can push jadeify through it
  6. I can enable source maps!!! debug: true

But mainly… its the one file thing, its driving me nuts how brilliant this. I thought requireJS was half decent. Now I realise that it was convoluted¬†¬†and bloody confusing at times

Being able to just use requires is really refreshing…

(function e(t,n,r){function s(o,u){if(!n[o]){if(!t[o]){var a=typeof require=="function"&&require;if(!u&&a)return a(o,!0);if(i)return i(o,!0);var f=new Error("Cannot find module '"+o+"'");throw f.code="MODULE_NOT_FOUND",f}var l=n[o]={exports:{}};t[o][0].call(l.exports,function(e){var n=t[o][1][e];return s(n?n:e)},l,l.exports,e,t,n,r)}return n[o].exports}var i=typeof require=="function"&&require;for(var o=0;o<r.length;o++)s(r[o]);return s})({1:[function(require,module,exports){
 * Created by Hutber on 10/12/2014.
'use strict';