Closed hoangnhan2ka3 closed 5 months ago
Btw, https://github.com/soranoo/next-css-obfuscator/issues/25 was fixed in v2.2.12
🚀
It's not fixed. It seems that the bug only appears in the part I mentioned above, in other components there are similar arbitrary classes like [&_{foo}]
but do not have the above error.
Not any behavior was changed in v2.2.13
compare with v2.2.12
ah, no, I was wrong
hmm what happen...
Since v2.2.12
, do you change any logic? because it was working on v2.2.10
(no problem with &
), and I'm using v2.2.10
for now.
As you can see there is no new commit. I just finished the PoC.
If there is any update, the related issue will be mentioned.
Or maybe the change of https://github.com/soranoo/next-css-obfuscator/issues/25 lead to this issue? Cuz in v2.2.12 | 13
https://github.com/soranoo/next-css-obfuscator/issues/25 was solved
But but, u say that u removed it huh?
The reason why #25 seems "solved" is I hadn't commented out all the code related to the previous buggy update. Additionally, I found there is one more "thing" related to this issue. Therefore, I can't push any updates before fully understanding what's going wrong.
The worst case scenario is because of the new obfuscation method
🥲 https://github.com/soranoo/next-css-obfuscator/commit/53ecb88985ed0ce6daf0357c2b35e157d3be2d25
But I don't see any conflict of the new method with the random
one.
I see many complex merge from https://github.com/soranoo/next-css-obfuscator/commit/374ba8c565f4ed8d784b87607a41f970bff6b271, did u check this? specially html.ts
(and related). One more case but I think it's not, is that because of Vitest =)))
Yeah! oh, but some not...
v2.2.14-beta.4
The core problem here is that the error just happens on reload, but if u move between pages, it's normal
Edit: I think it's not "some", nothing changed, I'm just so excited...
Edit 2: Oh but it works in v2.2.14-beta.2
wow
Okay, I've checked v2.2.14-beta.5
and it's works
Type
Checklist
Environment
Describe the bug HTML missed obfuscated (not happen with
v2.2.10
)To Reproduce
[&_h1]:font-semibold
IN THE FIRST LOAD. But when you try to move to another page or then come back to the page u visited previous, then u will see that style appliedExpected behavior In
v2.2.10
at hoangnhan.co.uk, it works perfectlyScreenshots ⛔![image](https://github.com/soranoo/next-css-obfuscator/assets/147973044/83ac11bb-6b63-453f-844d-3fd9384529f2)
✅
Config
Related files
Obfuscated version:
index.html.txt
Without:
index.html.txt
Demos (if any) N/A
Additional context
In output
index.html
: