Building for HTTP/2
It&#x27;s been found that resource concatenation is still more efficient <a href="http:&#x2F;&#x2F;engineering.khanacademy.org&#x2F;posts&#x2F;js-packaging-http2.htm" rel="nofollow">http:&#x2F;&#x2F;engineering.khanacademy.org&#x2F;posts&#x2F;js-packaging-http2....</a><p>And &#x27;building for http2&#x27; seems to be advocating hashes in filenames without neccesarily walking the dependencies, which can have cache problems <a href="http:&#x2F;&#x2F;holloway.nz&#x2F;r&#x2F;hashes-in-filenames&#x2F;" rel="nofollow">http:&#x2F;&#x2F;holloway.nz&#x2F;r&#x2F;hashes-in-filenames&#x2F;</a><p>ES6 imports are static (you can&#x27;t use JS to dynamically include a file) so this means transitive dependencies need to be resolved at build time, not by using a manifest file which resolves paths clientside. This also applies to (eg) SVGs that reference JPEGs because you probably don&#x27;t want JS involved there either. Manifest files are a bad idea, except perhaps for instructing webservers to tell browsers to preemptively download files. AFAIK there isn&#x27;t a standard for this yet so a manifest doesn&#x27;t solve the problem.<p>Ps. I&#x27;ve got a gulp build for http2-style packing and I&#x27;ll release it on my github in a few weeks (same account as my username)