RFC: When to do the initial build?

[Westbrook]

Issue

A number of different usage workflows quickly run into the possibility that the repo has not be built (yarn build) by the time that it is needed by an underlying script.

Possible solutions

1. Just add yarn build after yarn in the README.
   • Is that enough? Do people read READMEs?
   • If we do this, can we take yarn build out from in front of other scripts?
   • Has to possibility of having an out of date build if we remove yarn build from workflows.
2. Add a post-merge hook to husky that does it for us?
   • Does this run right after clone, do we need to yarn first?
   • Given changes could be incoming, should we yarn anyways?
   • Has to possibility of having an out of date build if we remove yarn build from workflows.
3. Expand all the scripts to yarn build before hand?
   • Could be done with pre* scripts...
   • Should we layer all scripts to a "user" version and a "ci" version?
4. Other options?

Notes

I do wish there were less steps to running our code in this repo, however we will need a build command for as long as typescript is as divergent from JS as it is a current. I'll leave moving away from TS for JSDocs based typing as a conversation for another day... 😉

[beeduul]

Solution 1 would have solved it for me. I was following the readme and it wasn't clear that I had to run yarn build.

There may be other good reasons for the other solutions.

[msdewey]

As @Westbrook and I discussed, it also seems like there are some issues with clearing the cache (had an incident where after building and running storybook, changes to a component where still not showing up until i manually ran build:clear-cache We may want to further look into determining the best time to wipe tsbuildinfo files

[Westbrook]

The approach in #265 should cover the bases on this request while also adding some new flexibility to the repo when addressing things slike #149. Please take a look when you have a minute.