Compiling static assets & incorporating tests

[searls]

Discuss how teams are currently compiling static assets for the web and how they might be improved, reviewing areas like:

• Asset fingerprinting, manifest generations, and CDNs
• Are builds progressive/iterative or all single-shot?
• What are your current feedback loop speeds in development, CI, and deployment?
• What are your biggest pain points?
• How are tests currently integrated?
  • is there a development mode that automatically runs tests on file changes?
  • do development-mode test builds require wasteful build activities take place that aren't necessary (e.g. styles/fonts?)
  • do tests run against the actually-built code or do they duplicatively build the code using their own test-scoped transpilers, potentially letting bugs through (e.g. how karma plugins tend to compile separately from the main app)

[ericgrigorian]

:+1:

[rmdonnelly]

:+1:

[dandumont]

:+1:

[pat-whitrock]

:+1:

[ghost]

:+1:

[vjmurphy]

:+1:

[julissa]

:+1:

[sheeralal]

+1

[ldeveber]

:+1:

[gmelville]

:+1:

[hparekh1]

:+1: