I agree that an error would be much better than the current behavior where it appears to work the first time you load the page / every time you try it out in development (with caching off) but then silently and subtly fails to work after it ends up in production (for every non-first page load).
Even better would be to actually support doing this (proposed here (and before that, here, etc.)). ![]()