Andy Ray

I'm just starting out with GraphQL, so I'm not sure if this is a correct line of thinking. This project already spins up its own private API service/process, [spun up...

Appears to be because you clear the modules after you process them? https://github.com/skozin/webpack-path-rewriter/blob/master/es6/index.js#L357

hmm - disabling hashing in dev sounds like a good idea. i'll try that and see if the whole thing works with that in place

**edit:** I did not read your other comment yet, looking at that now.. index.jsx: ``` require("../assets/index.html"); require("../assets/css/file.css"); ``` webpack config: ``` entry: { app: "./app/index.jsx" }, {test: /\.html$/, loader: PathRewriterPlugin.rewriteAndEmit({...

@sidorares have you gotten this to work with vanilla mocha? that's what i'm looking at now

Yes please! `ghci` is painful to use without `;`

[UserCSS](https://chrome.google.com/webstore/detail/user-css/okpjlejfhacmgjkmknjhadmkdbcldfcb) (Chrome plugin) theme to make Prisma's documentation in dark mode [in this gist](https://gist.github.com/AndrewRayCode/b2e96b5226b8dd7dcf950c9cd10372c4). Hopefully my poor color choices enrage the Prisma docs authors enough to make a better one!

@KiGniark no, it does not work with webpack 2: https://github.com/gowravshekar/font-awesome-webpack/issues/33

It would be a very minor upgrade to switch from this to ES6 modules, you'd just have to change the require() calls in here to import/export.

Also whatever builds the distributed bundle that's put into `build/` will have the correct configuration to sort out the require() calls. npm users will use the normal entry flow and...