There’s (recently) magic to do the caching Properly™, but for efficiency reasons and due to how we do the build, the assets are considered unchanged as long as the commit date is the same. So changing the assets and recompiling without committing will not automatically cause a browser refresh.
yep, normal dev workflow now… hack hack, ^S, swap window, Shift-Reload, tada!
Methinks the issue was the browser cache only, since strace -f -s200 -e file -o bla go run build.go assets told me it was reading my edited files
[meme] “I don’t always read man pages, but when I do, I tried strace first”