muito triste que meu site é em react e toda atualização que lanço ele sempre "atualiza" todos os arquivos e aqui aparece como se eu tivesse atualizado todas as paginas T.T
You could look up how to disable the hashing it adds to the names of JS and CSS files. It's done by default for a good reason though, so I don't think it's practical or advisable.
Well, it seems it is not that hard to do if you're using Vite: https://blog.livelyupward.dev/blog/remove-vite-hash Your also seem to have a chunk so you'll probably want to add `chunkFileNames` if you follow this route. Doing this means no more cache busting.
I'll look into this more, because I'm not sure removing the hash would really fix anything. Since the pages are loaded dynamically, the .html file itself doesn't change, so Neocities might not know which page was updated. But thanks :DDDDD
![.: [ pink + rabbit ] :. avatar](/site_screenshots/30/36/marbled/index.html.50x50.webp)
You could look up how to disable the hashing it adds to the names of JS and CSS files. It's done by default for a good reason though, so I don't think it's practical or advisable.
Well, it seems it is not that hard to do if you're using Vite: https://blog.livelyupward.dev/blog/remove-vite-hash Your also seem to have a chunk so you'll probably want to add `chunkFileNames` if you follow this route. Doing this means no more cache busting.
Yeah, I'm using Vite. I'm not sure if it's worth removing the hash, since it does help prevent incorrect page caching.
I'll look into this more, because I'm not sure removing the hash would really fix anything. Since the pages are loaded dynamically, the .html file itself doesn't change, so Neocities might not know which page was updated. But thanks :DDDDD