Levi Wheatcroft

These errors are generated by MemoryFileSystem which is no longer used in v2.

[v2](https://github.com/christophercliff/metalsmith-webpack/tree/v2) branch in this repo uses webpack 2, and has a variety of other improvements. You can install with `npm i --save github://christophercliff/metalsmith-webpack#v2`. It's stable, I'm using it in several...

I don't really understand the question, but I think this is an issue for webpack itself rather than metalsmith-webpack Maybe the webpack API has changed since v1, but the current...

This error was thrown because your node process tried to `mkdir /assets` in your root filesystem, which of course it doesn't have permissions for. The v2 branch completely refactors path...

Personally, I think the config passed to metalsmith-webpack should work whether passed to this module, or used externally by an npm script or something. Introspecting what a plugin user wants,...

Thanks for your interest, and suggestions! I'd prefer to avoid any additional versions of the 0.3.x branch. I haven't looked at it in ~5 years and wouldn't want to inadvertently...

Sure ok. Unfortunately I haven't really used superagent since I published this plugin. I'm sorry but it's more or less unmaintained at this time. As a workaround maybe you could...

PR #184 would allow something like this: ``` javascript var file = new static.Server('./public'); require('http').createServer(function (request, response) { request.addListener('end', function () { response.setHeader('Content-Type', 'text/html') // explicitly override header here file.serve(request,...

Currently no.. but PR #184 would allow something like this: ``` javascript var file = new static.Server('./public'); require('http').createServer(function (request, response) { request.addListener('end', function () { response.setHeader('Content-Type', 'text/html') // explicitly override...

Actually this issue is a dupe of #169