Would be great if one got a warning if a JS-file exists that has the same name as a UX-file but isn’t referenced from the markup. It is a silly mistake that is easy to make when refactoring.
Thanks for the suggestion. I’m personally not sure if this is generally desired. It makes a lot of assumptions about how you want your files structured, and it is equally annoying to get false positive warnings.
If this is an important thing to you, what about starting an open source community CLI tool that performs project folder analysis and gives hints on common mistakes? This doesn’t need to be built into the standard tool pipeline to be useful.
I won’t have the time to maintain such a tool, but perhaps someone else will in the future