-
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
Error when running 'gatsby develop' #307
Comments
grrr... things w/ that starter are messed up with npm 2.x right now. The easiest way to fix this for now is to upgrade to the latest 3.x npm ( |
Using npm 3 did the trick, thanks! |
I just run into something similar. Not sure if it is related to Gatsby at all, but posting just in case. Run Uninstalled Node with brew (see this) Reinstalled Node via the Mac installer from http://nodejs.org/. Now Gatsby works as expected! FWIW, this is what I did that didn't work and what happened: Relevant info: Following the basic steps from the tutorial, I get to This is what I get on the Terminal when running things:
|
my-test-gatsby-site prpatel$ node -v
v4.2.2
my-test-gatsby-site prpatel$ npm install -g gatsby
my-test-gatsby-site prpatel$ gatsby new my-test-gatsby-site
....
my-test-gatsby-site prpatel$ cd my-test-gatsby-site/
my-test-gatsby-site prpatel$ gatsby develop
Failed to require /Users/prpatel/dev/reactair/my-test-gatsby-site/html.js
./html.js
Module not found: Error: Cannot resolve module 'babel' in /Users/prpatel/dev/reactair/my-test-gatsby-site
resolve module babel in /Users/prpatel/dev/reactair/my-test-gatsby-site
looking for modules in /Users/prpatel/dev/reactair/my-test-gatsby-site/loaders
module variation babel-webpack-loader
resolve 'file' babel-webpack-loader in /Users/prpatel/dev/reactair/my-test-gatsby-site/loaders
resolve file
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader.webpack-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader.web-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader.loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-webpack-loader doesn't exist (module as directory)
module variation babel-web-loader
resolve 'file' babel-web-loader in /Users/prpatel/dev/reactair/my-test-gatsby-site/loaders
resolve file
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-web-loader doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-web-loader.webpack-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-web-loader.web-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-web-loader.loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-web-loader.js doesn't exist
/Users/prpatel/dev/reactair/my-test-gatsby-site/loaders/babel-
The text was updated successfully, but these errors were encountered: