Matt DesLauriers

If you `npm install devtool --save` you should be able to reference it by name. If there's still a problem could you put together a repo showing the issue? Here...

Can you put together a test case? I've never used cluster before.

I'm not sure if it's possible to do this programmatically.

Yep — Chromium DevTools is coming to node.js. :smile: Once it lands in Node stable, `devtool` will be mostly obsolete for debugging purposes. I'll update the readmes accordingly. But `devtool`...

I've tried adding that code to `server.js` and `preload.js` and I'm still getting an error using ServiceWorkers. Seems like an Electron bug? ``` GET file:///projects/jam3npm/devtool/test/fixtures/service-worker.js net::ERR_INVALID_RESPONSE undefined:1 Uncaught (in promise)...

See test here: https://github.com/Jam3/devtool/tree/test-service-worker

Can you try `2.0.2`? It should have a patch for this. To update: ``` sh npm install devtool -g ```

Ok, nevermind. Error is still there

This seems to be fixed in latest Chrome Canary (69).

I just released [shader-reload](https://github.com/mattdesl/shader-reload) which I'm using with [budo](https://github.com/mattdesl/budo) to achieve live editing of shaders. It involves splitting them into a separate module and attaching a transform on the browserify...