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
Closes #569 Add port process conflict resolution and Chalk #579
Conversation
Awesome! Could you add some screenshots? Since this isn't much code — how about you just copy/paste the necessary code into Gatsby for now and then in a follow-up PR we use react-dev-utils once the function is published? |
Okay I'll bring it over from |
Nah — just wanted screenshots to document here the changes you were making. Looks great. Once the tests finish running, I'll merge the changes and make a quick release. Thanks! This is a really nice little UX improvement. |
Released in 0.12.20 https://github.com/gatsbyjs/gatsby/releases/tag/v0.12.20 |
Hiya @vinnymac! 👋 This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here. Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! 💪💜 |
I tested this out, it seems to work great, but I had to add someone else's repo as a dependency because the
getProcessForPort
method hasn't been pushed to the officially availablereact-dev-utils
package on npm.I also added some chalk here and there.
If you want me to change the wording or add the dependency a different way let me know 👍