Title: I love JS, but every once in a while a new bundler comes along that &quot;solves everything&quot;. And it works, for a while. then it breaks. Why? Why are there so many edge cases? I don&#x27;t understand it. We only have a few module types (AMD, CommonJS, ES modules), with a few types of import and export syntax. How hard can it be to get it always right?<p>Like parcel. It worked. For a while. And now if you check the GitHub there&#x27;s 690 open issues, and I had issues today getting it to work when running after an &#x27;npm i&#x27; done in v17 or v18, yet it&#x27;s fine to run in v{16,17,18} if &#x27;npm i&#x27; is done in v16.<p>And snowpack: v0 (or 1) worked great, but the next version broke so many things (compared to the prior version) that I need to keep the dep version locked to the earliest ones for packages where I use that. Tho I guess that&#x27;s more of an API problem.<p>What I&#x27;m really talking about is: why can&#x27;t we just have a bundler that works always and everywhere (and I don&#x27;t want to &#x27;wait for&#x27; deno)?<p>Why would parcel start to get bugs...how hard can it be??? :...(
Upvote: