Reminds me of my recent issue with parcel, one those tools that it's supposed to make frontend development less messy that lets you start with no configuration,

Reminds me of my recent issue with parcel, one those tools that it's supposed to make frontend development less messy that lets you start with no configuration, I was in for a surprise, it does a lot of weird unexpected things with your code and files: - it changes the names of static files (e.g videos), if you put "type=module" on a script tag it deletes it (after investigating its due some incompatibility with how parcel works and top level awaits) - if you try to use any library that works on both the browser and node like fabricjs it fails at compile time (some parsing goes wrong), if you try to find some way to ignore such files you discover the only way is to host that script online because parcel doesn't touch these - if you use shadow Dom in your app it appends everything inside those twice when hot-reloading modules (tbf that has an easy solution that listens, to listen a parcel event to force a reload, about 3 lines of JS) And some other smaller issues, in conclusion it was a mistake, I converted it to webpack an it works all better now, I should have gone with webpack from the beginning and avoid things I haven't used before just from fake promises of simplicity.