Vladimir Agafonov
Vladimir Agafonov
@francoismassart Yeah, it works, but it causes a problem elsewhere: ``. ``` ESLint stack trace: TypeError: p.value.split is not a function Occurred while linting Test\index.tsx:23 Rule: "tailwindcss/no-contradicting-classname"... ```
This would also work well with `add*` functions and such, but I don't see a way to do it without breaking the current design. Unless you use an explicit `null`...
Hey @francoismassart. Is there any progress on this topic? The solution with `callee` looks rather redundant and unfortunately is not applicable in real projects with thousands of classes.
[`sveltekit-superforms`](https://www.npmjs.com/package/sveltekit-superforms) - https://github.com/ciscoheat/sveltekit-superforms/issues/426 - incompatible in rune mode for the entire app.
[`svelte-highlight`](https://www.npmjs.com/package/svelte-highlight) - incompatible in rune mode for the entire app, but there is a compatible alternative - [`svelte-rune-highlight`](https://www.npmjs.com/package/svelte-rune-highlight)
> I fear tailwind's micro syntax might grab this character at some point, too https://play.tailwindcss.com/a6j1Ed7RF2 ``` A B ``` Tailwind has had the ability to use CSS inside its classes...
Why not just use class (attribute) syntax with directives? Either make quotes mandatory or optional. Based on the example above: ``` class="w-1/5" class:"md:w-10/12 lg:w-8/12 2xl:w-6/12"={someVar} class:lg:w-10/12={anotherVar} class:2xl:w-8/12={yetAnotherVar} ``` `class:"..."` will...
Hi guys. This long awaited feature seems to be stalled due to a rather non-trivial issue. Maybe it's possible to separate relative time parsing into a separate issue and release...
https://bugs.webkit.org/show_bug.cgi?id=242740 - I encountered the same problem. Getting rid of top-level `await` helped. P.S. The problem is reproduced only in Safari 🤬, in Chrome and Firefox everything is ok.
https://github.com/sveltejs/svelte/issues/3311#issuecomment-573306447 - additional information on the topic.