JavaScript import maps are now supported cross-browser
Does this mean that in theory i could skip the build/bundling step entirely?<p>E.g. i could have a backend project in whatever language i wanted but then instead of having an npm frontend project, instead i could:<p><pre><code>    1. use a jsconfig.json and jsdoc to gradually type with typescript but without need for tsc since my editor gives me feedback anyway 
    2. use es modules to handle splitting and caching the various .js files of my app
    3. use this import maps feature so that i can still gzip and add the digest of the file to the filename so that i can safely say cache every .js forever since if theres a change, the filename will differ and this feature means i can still import from friendlyname rather than friendlyname-hashed-value
</code></pre>
What am i missing from the bundle approach:<p>Optimal file transfer - all in one js bundle, but if i have http2 then i don’t care because the overhead of multiple files is gone<p>minify - i don’t care since i gzip anyway<p>sourcemaps - i dont care since the files presented to the browser are the ones i wrote, maps are redundant<p>I quite like react but i think i’d like simplifying my tool chain more and using something like htmx instead.<p>EDIT: i want to qualify the “i quite like react” statement, i have pure components only, no useState, for state handling in the small i’m fine with pure useReducer’s but zustand is nicer for my cases since i can also use that to prevent subtree re-renders of the reducer/context barebones approach.