I think it’s probably because the images were being referenced in the HTML of my tabs pages (i.e. tab-map.html) which live in /www/templates, so there must have been a difference when serving the app in Chrome/Safari vs. actually building the app with regard to where the app thinks its “location” is. That could probably be worded a lot better than how I just attempted to say it
Before, I had to jump out of the templates folder to get into the img folder, “…/img/pic.jpg” because when it was being served, it recognized its current state as being in the templates folder. Whereas once it’s built, it recognizes itself as root.
That’s my guess.