Andres Suarez

Actually seems like Sublime is not assuming `false` for settings that it doesn't recognize. If you add this to your `Preferences.sublime-settings`, it looks ok again: ``` "soda_retina_fix": false, "soda_classic_tabs": false,...

As the maintainer of babel-sublime, I can confirm that we will not support CJSX. If sublime-better-coffeescript takes on supporting CJSX, I'd be more than happy to drop in note in...

Thanks @deoxxa!

@Niondir: `/** @jsx React.DOM */` is going away in React 0.12 http://facebook.github.io/react/blog/2014/10/16/react-v0.12-rc1.html#the-jsx-pragma-is-gone

Sorry I don't have time to implement this. I will however review a carefully though out and thorough PR that implements this.

Sure, I like the idea. But can it take an string or array of strings instead with each extension instead? Also, it should override the default.

@simonzack The use case for this (according to https://github.com/substack/watchify/issues/56) is for when you use watchify via the command-line. How about if in `bin/cmd.js` you handle the tearing down the previous...

@jmm, ignore what I said in https://github.com/substack/node-browserify/issues/1282. I'm ok with this order. if you're cool with it too, then I'll merge it

@jmm that test is too specific, and too big - remember, this gets added to every module that references `global`. if there's a global object called `window`, then you've got...

> What makes it too specific (disregarding length)? It could be less specific than that yet still more specific than just window (e.g. window && window.document) I don't feel it's...