next-css-obfuscator: Incorrect Class Conversion Table Generation
Sorry, I have a problem unrelated to this issue, which is caching.
You know, every time you run build the obfuscate process will start from the beginning, meaning the random obfuscated classes will be completely different from the previous time. This causes nextjs cache related issue.
If a user has visited my page before, then after I update (new deployed), and they reload the page without clearing the cache, it will look like this:
And no matter how many times they try to ‘refresh’ the website, it will still look the same.
Unless they press Ctrl + Shift + R (aka hard reload), the site is updated.
Even when I try view page source without hard reload, the css file doesn’t have any new obfuscated class, which causes an error like my website doesn’t have css at all.
Do you have the same problem in your version of Next Js, or do you have any advice for me, I’ve been searching for it all night.
_Originally posted by @hoangnhan2ka3 in https://github.com/soranoo/next-css-obfuscator/issues/10#issuecomment-1925819091_
Additional Infomation-
- Obfuscated selectors got obfuscated again
conversion.json
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 52 (21 by maintainers)
Why don’t I make your wish come true instead of explaining it in a text?
Let’s move to #14
@hoangnhan2ka3 Check out the latest update, and the following https://github.com/soranoo/next-css-obfuscator?tab=readme-ov-file#6-how-to-deal-with-css-cache-in-paas-like-vercel
Hope this can help you out.
not now, I may do it after fixing the Partial Obfuscation
predictablesame input same output