Ship 4.0.0

[zertosh]

Before closing out 3.x:

• Merge Properly handle exposed modules #199 (blocked by Fix mysteriously disappearing "expose" and "entry" module-deps#80)
• Some version of Add version option #197 (blocked by Remove 'v' shortcut for version browserify#1222)

4.0.0:

• Manage own ignoring instead of with chokidar #212 - Handle ignore logic inside watchify instead of delegating to chokidar. Essentially some form of Add/ignoring handler #202 (comment). This will bring the semantics of ignoring inline with browserify.
• Drop watchify.args (see Make args a function, to prevent inadvertent sharing of caches across instances #204). Sharing caches is a bad idea for most users. Turning off the cache, or using your own cache will be an opt-in.

[zertosh]

@jmm I think the 4.x line will be the last one before the row biz is figured out. So 5.0 is hopefully where we reconcile browserify + watchify + module-deps w.r.t. to the row api.

[mattdesl]

👍

Just so I'm clear, the following will still work in 4.x correct?

var b = browserify({ cache: {}, packageCache: {} });
var w = watchify(b);

[zertosh]

@mattdesl It will. But it I can't actually get rid of having to pass a { cache: {}, packageCache: {} } somehow into browserify like I wanted in #204 (comment).

[jmm]

@zertosh What's the upshot of that -- will watchify.args be sticking around in some form?

[zertosh]

@jmm The cache object gets passed to module-deps when a pipeline is created (grep mopts). By the time watchify is applied to browserify, a pipeline already exists. So I'd have to dig into b.pipeline get module-deps, and modify its options object. Not cool.

But we need some form of watchify.args that creates new cache objects - like your PR. Though, that kinda sucks because if someone keeps using watchify.args, it won't break - it'll just silently not cache. Unless we do something like:

watchify.args = function() {
  return { cache: {}, packageCache: {} };
};
xtend(watchify.args, watchify.args());

But if users have to change from watchify.args to watchify.args() (or something else), maybe we should leave it as it. Instead change the documentation here, gulp, etc. to explicitly pass {cache:{}, packageCache:{}}.

[jmm]

@zertosh Ok, thanks, I figured that's what the issue was. I posted some ideas in #204 (comment).

[zertosh]

Closing this out for now since things still need to be figured out in browserify regarding path matching.