Nik

@skvav может рассказать из какого api вытащить principals 😉

Yep, that one was created in load channel callback Regards, Nikita > On 28 Apr 2021, at 14:16, Andrey Sitnik ***@***.***> wrote: > >  > Am I right that...

I’d likely make a PR if you have a good idea how to improve it and not make it worse😅 Making this non-fatal? Leaving it fatal but with better error...

Seems relevant to me. Was first quite surprised with current behavior, then surprised when I found some kind of evidence it’s not a bug in https://logux.io/recipes/cross-tab/ > All tabs will...

(Right now I have to patch/opt out of CrossTabClient just because of that unisolated subs thing)

I'd suggest looking how tailwind cli itself handles imports like these before reinventing the wheel. I've caught the same issue — `npx tailwindcss` cli works ok, `npx tailwindcss-classnames` fails. Btw...

> > Btw why don't you use `./tailwind.config.js` config path as a default? > > I'm not sure if I understand this correctly, could you please elaborate more? `./tailwind.config.js` in...

``` npx tailwindcss-classnames -i app/styles/index.css [UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled...

Still the same result when executing via `npm run x`. Error reporting is not clear enough (swallows details) to understand what is going on without digging into sources ``` npm...

Ah yep that appears to be mine: config part referencing `process.env` seems to be the reason. BTW in my case it's impossible to configure tailwind correctly without reading env vars....