Working on a preact app, presumed it was preact doing this.
Looks like directly in the iframe there is a reference to a relative path to:
3.bundle.js which for some reason in firefox add’s it to my head element causing a 404.
It seems like chrome is clever enough to ignore this but firefox appends to the
Github issue I made: https://github.com/preactjs/preact-cli/issues/1378
Please can this bundle use an absolute path, or, just remove it as looks to be 301ing to nowhere anyway???
I ran into this too while auditing server error logs. It’s creating quite a bit of noise.
It does seem that the reference to 3.bundle.js can be safely removed since it’s not there anyway.
This is a very annoying bug,
3.bundle.js keeping spoiling the server logs and and its a shame default patreon web widget keeping popping this error on both chrome and firefox for me. devs please fix this.
for reference embed this in any html:
<a href="https://www.patreon.com/bePatron?u=45118317" data-patreon-widget-type="become-patron-button">Become a Patron!</a><script async src="https://c6.patreon.com/becomePatronButton.bundle.js"></script>
8 months later, and this is still an issue. Do we need to become a patron of Patreon’s developers for them to fix this?
There should be no references to my site’s file system. Also, they are distributing code with references to .js.map files, but then blocking access to those .map files.