Widget iframe makes request to a missing bundle with a relative path in firefox

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 head

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???

1 Like

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.

1 Like