# Source Map Loading Errors

**URL:** <https://discourse.nodered.org/t/source-map-loading-errors/101882>\
**Category:** General\
**Created:** [9 October 2026 16:22 UTC](https://discourse.nodered.org/t/source-map-loading-errors/101882 "2026-10-09T16:22:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MakerMan](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@MakerMan](https://discourse.nodered.org/u/MakerMan)\
**Post date:** [9 October 2026 16:22 UTC](https://discourse.nodered.org/t/source-map-loading-errors/101882/1 "2026-10-09T16:22:12Z")

</div>

Browser is Safari 27.0.1 on MacOS latest release.  
Running NodeRed 5.0.8 on RPI (Debian Trixie)

What I'm finding is that Node Red screens are continually fully refreshed when selecting a tab. Every time it refreshes it returns to the first tab, so I can't actually get at tabs to change nodes etc.

The Safari debug shows lots of 404 errors - unable to load map files (which don't exist).  
e.g. ```Cannot GET /vendor/purify.min.js.map

This used to work fine but some recent upgrade has clearly broken this.  
Any ideas as to how to fix this?

Thanks

---

<div class="post-metadata">

**Author:** ![mbonani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mbonani/32/10631_2.png) [@mbonani](https://discourse.nodered.org/u/mbonani)\
**Post date:** [9 October 2026 17:31 UTC](https://discourse.nodered.org/t/source-map-loading-errors/101882/2 "2026-10-09T17:31:12Z")

</div>

Please check this previous post about it.

> [@Odd behaviour or error with Safari 27 on Mac](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788):
>
> My Mac updated to Safari 27 today and now I get an annoying behaviour. When I first open the NodeRED editor in a fresh Safari I can't navigate away from the first tab. Whenever I click another tab it displays the new tab and then an error causes Safari to reload the page which takes me back to the first tab again. It isn't catastrophic because oddly if I manually reload the webpage the problem goes away. After messing around with the dev console settings I managed to catch the error that seems …