Issue using vbuild as a local dependency

[egoist]

Issue using vbuild as a local dependency

[egoist]

OK, when you install vbuild as devDependency I guess webpack-hot-middleware is installed under your-project/node_modules/webpack-hot-middleware instead of your-project/node_modules/vbuild/node_modules/webpack-hot-middleware (because of npm 3's flat directory structure).

And we use __dirname of vbuild to resolve webpack-hot-middleware, that's why this issue occurs, will fix it.

[egoist]

@neves fixed in v3.1.5

[zephraph]

Oddly enough, going into the vbuild directory and issuing npm install fixes the issue. It looks like certain items are expecting an absolute path to exist when it may not.

[neves]

This problem persist with vbuild 3.1.4
reproducible code:

npm i -g vbuild
vbuild init bug
cd bug
npm i -D vbuild
npm i
npm run dev
...
ERROR in multi client
Module not found: Error: Can't resolve '/.../bug/node_modules/vbuild/node_modules/webpack-hot-middleware/client' in '/.../bug'
 @ multi client

# using vbuild --dev globally works fine
vbuild --dev

[zephraph]

Must be a new thing. It was resolved. @egoist is probably in bed, I'll take a look at it soon.