Blip's webpack build
Our usage of the webpack module bundler at Tidepool is pretty standard, but there are a few things worth noting:
<text>in SVG is not as fun or easy as it is in HTML.) We found that we could avoid this UI "jump" of elements by simply splitting off the CSS (including the
@importstatements for our fonts) into a separate file. The browser doesn't paint until the CSS is fully loaded, and we no longer have UI "jump".
Mess with the
resolveLoaderconfiguration options at your own peril! These are essential to being able to
npm linkblip's "child" repositories (currently tideline and viz) when working locally.
[💣 tech debt 💣] Our production webpack build could be optimized quite easily to make our bundled assets smaller and faster to load. We're not doing many of the things common in production builds such as uglification and minification.
[💣 tech debt 💣] The webpack.config.js file is long and hard to follow. It would serve us a lot better if we divided the dev build and the production build into separate webpack configurations in separate files.