Not able to start dev server in /www #9640
Labels
status: awaiting author response
Additional information has been requested from the author
Comments
|
@pranshuchittora yeah, it's a little unfortunate. In general, the site showcase (and taking screenshots) is the bulk of the time spent there. It'd eventually complete, just takes quite a while. Can you try this setting? The general idea is you'd create |
DSchau
added
the
status: awaiting author response
|
Sounds like that worked, so closing out! |
|
Thanks @DSchau it working 馃憤 |
|
Consider these updates in the docs #9643 馃憤 |
DSchau
pushed a commit
that referenced
this issue
Nov 1, 2018
Recently I tried to run the instance of gatsby's website locally. By using `gatsby develop` in /www, unfortunately, it got stuck. Refer #9640 for more info. Thanks to @DSchau he suggested trying `GATSBY_SCREENSHOT_PLACEHOLDER=true` to run the dev server. But for a new contributor, it's hard for him to figure this out. So I made some changes in the `how-to-contribute` docs.
gpetrioli
pushed a commit
to gpetrioli/gatsby
that referenced
this issue
Jan 22, 2019
Recently I tried to run the instance of gatsby's website locally. By using `gatsby develop` in /www, unfortunately, it got stuck. Refer gatsbyjs#9640 for more info. Thanks to @DSchau he suggested trying `GATSBY_SCREENSHOT_PLACEHOLDER=true` to run the dev server. But for a new contributor, it's hard for him to figure this out. So I made some changes in the `how-to-contribute` docs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today I tried to run the instance of gatsby website locally.
It stucks at
source and transform nodes馃槥Pls refer this screenshot 馃憞
The text was updated successfully, but these errors were encountered: