JavaScript component filenames become invalid after hash salt change/rotation

balintbrews → credited amandeep singh → .

balintbrews → credited attilatilman → .

balintbrews → credited mglaman → .

balintbrews → credited penyaskito → .

Crediting people who participated in the conversation that resulted in this issue.

I've pushed a proof of concept of removing the hash by the original id.

I've adapted the tests and expected more things to break but they don't.

1. I've created a code component named nachojs and added to components. XB created default/files/astro-island/nachojs.js well.
2. I've modified the nachojs.js file title "nachojs changed title" and it changes well.

I've run all the tests that I've modified and all pass (except for those hash/filename that I expect), but I'll let the CI to run the whole battery.

One thought I had was keeping a hash, but making it a hardcoded salt. So v0, v1, v2, etc. Whenever XB has a breaking change, this could be bumped and an upgrade hook written. No idea _why_ a breaking change could happen, but it is atleast an option to load different files?

This looks surprisingly simple! 🤯

Just one Q. 😊

🏓

This looks simpler & more elegant than I dared hope! 😄

Thanks!