Optimize Storybook for quick startup; Convert Storybook config to TS.

[sawyerh]

Ticket

Closes #21

Changes

• Enable Storybook's lazy compilation and filesystem caching. These two features improve the startup time (mostly noticeable for larger projects).
• Convert the Storybook config file to TypeScript to receive type checking. This can help catch invalid or deprecated config options.

[aligg]

Does lazy compilation mean basically that a story will only compile when the browser requests it to load?

I was reading this: https://storybook.js.org/blog/storybook-lazy-compilation-for-webpack/ and the explanation felt slightly different than this https://webpack.js.org/configuration/experiments/#experimentslazycompilation so just wanted to understand.

[aligg]

Trying to think of a usecase where projects wouldn't want this. I feel like for the claim status prototype for example we might not want it if we anticipate folks would try every single claim status option (OR would that be fine b/c they are all the same page so all the options would be compiled already)

[sawyerh]

Does lazy compilation mean basically that a story will only compile when the browser requests it to load?

Yea this was my understanding based on their post. I agree the webpack doc is kinda confusing.

I feel like for the claim status prototype for example we might not want it if we anticipate folks would try every single claim status option

I don't think this is an issue since lazy compilation only impacts how stories compile during local development (npm run storybook), but for the published Storybook, those are all compiled at build time (npm run storybook-build)

[aligg]

oh right! thank you sounds good!