Users should experience hot reloading as soon as possible

[marisamorby]

Description

Users should experience hot reloading as soon as possible because it is a crucial taste of the important value that Gatsby provides--fast in every way that matters. A faster editing/development cycle is a huge part of why people like Gatsby, but we don't yet know how fast the cycle is and whether we could make it faster.

Measure how long it takes from the time people install Gatsby CLI until they visit localhost:8000 (after running gatsby develop). We want to know how long it takes before people get their first rewarding "wow" moment so we have a baseline to measure against as we try to reduce that amount of time.

Actionable steps

@jamo to figure out how to measure this

After this issue is done

After we have a baseline measurement, we can figure out if we can/should help people experience hot reloading even faster than they do now and we can decide the steps to reach that goal.

Note:
This is replacing issue https://github.com/gatsby-inc/mansion/issues/3422 (Set up goals for OSS funnel and alerts when we don't meet the goals).

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[sidharthachatterjee]

Closing this for now since:

• we measure much of this in telemetry
• this issue mentions what but doesn't illustrate how which I think is crucial in this particular instance