-
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
First time expereince: WebpackError: ./.cache/develop-static-entry.js #10456
Comments
@stereobooster i'm cloning your repo and picking up from there and see if i can help solve this issue. What i would like for you to do beforehand is update your repo with the current version of the code, when you started having issues if you don't mind. |
Updated
|
@stereobooster ok, good that updated the dependencies, but following the tutorial i was unable to reproduce your issue, everything worked out perfectly. And like i told you before, push your code to the repository that is giving you this error, so that i can take a look at it. This because the present code you have does not include this. It's the standard starter code. And i would like to see the actual code that's causing this, so we can resolve this. Sounds good? |
I did it. This is the code which produce the error. You are saying that you can't reproduce it? I guess issue is in my machine. The problem is that I can't fix it by removing |
@stereobooster when i asked for the update on my previous comments, was based that you were having issues when you created the graphql query and then issued |
I had the same problem and fixed putting this on babel configuration: "babel": { |
This problem gets more acute if |
thank you timothy, this totally fixed my issue |
@timotta that also fixed it to me, thanks! |
Description
I followed step by step tutorial. When I got to this point https://www.gatsbyjs.org/tutorial/part-four/#your-first-graphql-query.
I started to get this error:
I tried to delete
.cache
andnode_modules
didn't help.Steps to reproduce
Expected result
developer server should start
Actual result
developer server doesn't start
Environment
The text was updated successfully, but these errors were encountered: