Every time I push a new release to main, wasm-pack runs in the GitHub Actions environment to completely rebuild the Wasm component of Doclight which probably hasn't changed any. This means that the deployment takes a long time, which admittedly isn't a huge deal, but also because wasm-pack timestamps the build or something, the wasm file changes slightly every time it's built, which means the service worker has to download a new wasm file that does the exact same thing. So that's not great. There's a way of caching it but I'm not sure how to tell it not to run the build if the cache hits and it's not a huge priority right now but probably later?? Also I'm tired and I realize I was supposed to leave Doclight alone for a while but apparently my brain is like let's work on Doclight some more!!
Every time I push a new release to
main,wasm-packruns in the GitHub Actions environment to completely rebuild the Wasm component of Doclight which probably hasn't changed any. This means that the deployment takes a long time, which admittedly isn't a huge deal, but also becausewasm-packtimestamps the build or something, the wasm file changes slightly every time it's built, which means the service worker has to download a new wasm file that does the exact same thing. So that's not great. There's a way of caching it but I'm not sure how to tell it not to run the build if the cache hits and it's not a huge priority right now but probably later?? Also I'm tired and I realize I was supposed to leave Doclight alone for a while but apparently my brain is like let's work on Doclight some more!!