Watchify support

Question

Watchify support

maxkfranz opened this issue 8 years ago · 3 comments

Since this is a wrapper around Browserify, is it possible to use Watchify with it out of the box?

It would be nice to be able to

(1) use watchify in npm scripts, and

(2) have the b = browersify() instance exposed somehow in the JS API for Splittable such that I could hook up Browserify and Watchify manually in JS (as you would in a gulpfile.js).

Answer 1 · 2016-12-08T17:18:43.000Z

It would be possible, but overall I think that splittable is too slow for development. It is a bit unfortunate not to have a fast mode available.

Answer 2 · 2016-12-08T17:45:22.000Z

One of the slowest part about Browserify is bundling all the dependencies from node_modules. Is is possible to put all node_modules dependencies in a single dependency bundle to speed things up for development? The dep bundle would rarely if ever change.

If there are other features that are expensive (maybe tree shaking), there could be flags to turn those features off for when developing to speed things up.

Alternatively, Splittable could just extend/subclass the existing Browserify API. That way, a build process could just swap out the Splittable object with the vanilla Browserify object for fast development builds.

What do you think?

Answer 3 · 2016-12-08T18:26:13.000Z

It could certainly be sped up by making the closure compiler build non-optimized. What would be better, indeed, if browserify could output bundles directly. That would be a bigger project if even possible.

…

On Thu, Dec 8, 2016 at 9:45 AM, Max Franz ***@***.***> wrote: One of the slowest part about Browserify is bundling all the dependencies from node_modules. Is is possible to put all node_modules dependencies in a single dependency bundle to speed things up for development? The dep bundle would rarely if ever change. If there are other features that are expensive (maybe tree shaking), there could be flags to turn those features off for when developing to speed things up. Alternatively, Splittable could just extend/subclass the existing Browserify API. That way, a build process could just swap out the Splittable object with the vanilla Browserify object for fast development builds. What do you think? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFeTxsHdYjH3E0VGOtu6d4uhfTpHN4_ks5rGEIygaJpZM4LIED2> .