Oleksandr Fediashov

> i have same error this is my log file https://filebin.net/92oynzeaigg9dzlb/log.txt It's not the same error, please create a separate issue and provide a minimal reproduction case.

@lokeshwarobuli I have managed to make it working, here is an example: https://stackblitz.com/edit/vitejs-vite-mvpj3w The proper config is: ```ts import { defineConfig } from 'vite'; import linaria from '@linaria/vite'; import react...

This is a valid issue and happens with v5. It happens when an expression is not referenced, i.e. ```js // FAILS 💥 const title = css` font-size: 24px; font-weight: bold;...

v4 & v5 use Babel heavily as a AST parser, if support for your language features can't be configured through Babel - I don't think that we can do much....

The issue was updated to propose extending existing imperative handle. With the previous proposal (functions) we cannot handle updates of refs properly.

@ecraig12345 is it possible you prioritize this? We have already met this problem, for example, in #19281.

@SukkaW Griffel now has support for CSS shorthands in #531, the most of `shorthands.*()` are now deprecated, we don't plan to publish them.

> Any update on the vite plugin? As [wyw-in-js](https://github.com/Anber/wyw-in-js) is out, I can rollout the plugin finally 🎉 I reworked original PR (#41) and it can be shipped once the...

FYI #41 was merged and plugin will be available on NPM today. It does not support CSS extraction, yet (#494).

@SahilTara I will talk with @microsoft/teams-prg to prioritize it.