Lutymane
Lutymane
Thank you! I realized the main issue in my edits was that my custom `TOKEN`(s) were defined after `TOKEN.HASH`/`TOKEN.*_ANGLE`, thus it broke. It must be defined before them. Regarding new...
Or use `fixupPluginRules` from `@eslint/compat` package
Web component, exposed method to set the shader or use attribute with id if it’s published
I did more investigation and found the cause finally. I use `build.target: "esnext"` in Vite and following their source code, Vite passes empty object to `targets` option for lightningcss. So...
Hmm but isn't it counter intuitive? Since if you don't supply the target that means you don't know which browser will use the code, thus it definitely shouldn't remove anything...
Any progress for Brotli support?
Having the same issue! Surprisingly with a plugin of very similar concept haha. It occurs when doing any changes to the Vue SFC. I can see HMR grabs original file...