-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work when installed with npm 3.x #19
Comments
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. |
Despite several attempts, I've been unable to reproduce this. Can you give me more details about the problems you're seeing? |
When doing
|
Probably because npm@3 dedupes stuff. |
I have the same issue here on Arch Linux with npm 3.4.0. |
Fixed in #102. |
@fson Any reason to keep this issue open? |
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. |
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.The text was updated successfully, but these errors were encountered: