Forbes Lindesay

Yes, it can be made configurable. Ideally we'd do something to figure out the correct default. Perhaps on startup it could write a temporary file, see if chokidar detects the...

I wonder if we could just: 1. poll much more slowly, but still poll even when it looks like we don't need it? 2. allow passing through "watchOptions" as an...

It's an option. It's not actually quite as powerful as you'd think though. Browserify lets you put some options in the call to `.bundle` so we's probably end up needing...

Have you tried passing the fully resolved names to browserify-middleware? This really should be achievable without browserify-middleware accepting a bundle.

You could just do: ``` js Server.prototype.serveBundle = function(app) { app.get('/mqtt.js', browserify('mows', { standalone: 'mqtt' })); }; ``` Unless there's also a library at `__dirname + '/node_modules/mows/index.js'` it should resolve...

It should work now, I don't know why it didn't when you first tried it. If it doesn't you can always do: ``` js Server.prototype.serveBundle = function(app) { app.get('/mqtt.js', browserify(require.resolve('mows'),...

What's the exact code at `/Users/matteo/Repositories/mosca/lib/server.js:393:23` Note that it must be `'mows'` that you pass to browserify and not `'./mows'` It uses the module resolution algorithm from node.

Ah, I thought we were using the node.js resolution algorithm, turns out we do just join the paths, so you were right all along, my apology.

I'd happily accept a pull request. I'm not really actively maintaining browserify-middleware anymore, but I will continue to merge pull requests. It's great to hear that uglify-es has a maintainer...

I still want us to detect changes to node_modules by default, maybe we could be a bit more clever about it though (maybe only poll every 5 seconds or something).