You would need to require both of them in <xf:js> tags, in which case they should be loaded in order:
<xf:js src="xf/form.js" min="1" />
<xf:js addon="My/AddOn" src="my/addon/my-js-file.js" min="1" />
I believe we already show errors and warnings before installation if hashes.json is missing or if the files don't match up, but in development mode you can choose to force the installation anyway. In production, blocking the add-on from being installed is deliberate. In development mode, you...
You shouldn't need to do manual file or directory removal in your uninstall routines unless the add-on creates files at runtime (user uploads, etc.). XF presents the option to remove all files from hashes.json automatically after uninstallation. I think it will leave any directories even if they...
Hundreds if not thousands of add-ons have been packaged and released this way, and I don't remember any similar issues coming up so I'm really not sure what the issue could be. Have you tried installing the add-on on a different XF installation to see if it's an issue with that particular XF...
I'm not overly concerned with it personally. We can reassess in a week, after which point the score should be derived from views of logged in members only.