Doesn't work when installed with npm 3.x

[andreypopp]

File webpack.config.coffee assumes too much about how npm layouts modules when installing them. npm 3.x is radically different than npm 2.x in this regard and so gatsby doesn't work.

Suggestion is to use require.resolve instead of relying on ../../node_modules paths (webpack-dev-server entry points). resolveLoader.modulesDirectories also needs a tweak.

[KyleAMathews]

Thanks for the report! Will work on this later. From Slack discussion, it sounds like I started the project on NPM 2.x then moved to 3.x which means the old npm node_module structure was retained.

[KyleAMathews]

Despite several attempts, I've been unable to reproduce this. Can you give me more details about the problems you're seeing?

[freiksenet]

When doing gatsby serve

Uncaught Error: Cannot find module "node_modules/gatsby/lib/utils/../../node_modules/webpack-dev-server/client?0.0.0.0:1400"webpackMissingModule @ multi_main:1(anonymous function) @ multi_main:1(anonymous function) @ bundle.js:551__webpack_require__ @ bundle.js:521(anonymous function) @ bundle.js:544(anonymous function) @ bundle.js:547

[freiksenet]

Probably because npm@3 dedupes stuff.

[frol]

I have the same issue here on Arch Linux with npm 3.4.0.

[fson]

Fixed in #102.

[scottnonnenberg]

@fson Any reason to keep this issue open?

[fson]

We've been using Gatsby with npm3 for a few months now, and it should work without problems.

We can always open a new issue, if some specific problem is discovered.