Valerii Strilets 🇺🇦

A new journey has begun, and I am very happy that everything went almost as I planned. There was only one downtime of individual features lasting 10 minutes, and no other problems. So I look forward to seeing you at conar.app, conar.ai, or conar.dev 😁

DANGEROUSLY_useState

Let Matteo write that the problem is due to Webpack

@pacovitiello @coss_com Thanks, looking forward to it

@letstri @coss_com Love the shadcn update! A bit busy with a few other tasks atm but definitely looking into it shortly

Just dropped the @coss_com Drawer component 📦✨ ✅ 4 directions + 3 built-in variants ✅ Snap points & Nested support ✅ Swipe-to-open area ✅ Responsive examples (Dialog & Menu → Drawer)

I love modern libraries just look how beautiful it is 🔥

@matteocollina @nodejs Huge

.@nodejs has always been about I/O. Streams, buffers, sockets, files. But there's a gap that has bugged me for years: you can't virtualize the filesystem. You can't import a module that only exists in memory. You can't bundle assets into a Single Executable without patching half the standard library. That changes now 👇

The library is getting better. Now you can create a subscription, base a computed value on it, and then use it via a hook or component.

@DmytroKrasun Sure, I’m sponsoring

@letstri Do you use it, too?

Refactored Server Actions (Next.js) to oPRC. And damn, I envy AI that it will write code for me. The type safety and ergonomics are so sweet, it makes me want to code manually again.

harry styles is a fucking badass

@aidenybai do I need buy a sub for it? 😁

Introducing element-source Get the source file location of any DOM (or native!) element Works w/ React, Vue, Svelte, and Solid

With Seitu, you can create a subscription and use its value directly in the component.

@alexandereardon is it next js?

Optimistic navigation updates

@william_ma14406 @kysely_ @prisma I understand that you wanted to add a query builder, but installing a dependency on another ready-made builder and thereby simply bloating your library is strange. What prevents me from simply installing Kysely separately and using it? Only the types generated via Prisma?

@letstri @kysely_ @prisma Prisma Next treats the query builder as a swappable component, not baked into the framework. The query builder pictured here is derived from Kysely, because it was easy to get up and running, but you can use any query builder with PN that can produce our AST

I wrote this code using @kysely_ I never said anything about @prisma because they make a cool product. But now it's just Kysely.

@markccalugay I didn't even think about it at all 😁

@letstri Aye yo that power cable! bro did it for engagement haha I was totally triggered 😂

Rate my new setup We moved from Kyiv and now I'm working among the boxes in the kitchen

@kianbazza @tailwindcss @shadcn Oh, sure, I’ll reinstall it, thanks!

let's goooo 💪 also it seems like I left some dead code in there 😬; feel free to re-install to remove the --𝚑𝚒𝚝-𝚊𝚛𝚎𝚊-𝚋𝚕𝚎𝚎𝚍-* related code may release that as an add-on later the intention was to add a 𝚑𝚒𝚝-𝚊𝚛𝚎𝚊-𝚋𝚕𝚎𝚎𝚍-* utility to add "extra" hit area to account for borders, instead of doing "𝚑𝚒𝚝-𝚊𝚛𝚎𝚊-𝟺.𝟸𝟻" which may not read as well you could do "𝚑𝚒𝚝-𝚊𝚛𝚎𝚊-𝟺 𝚑𝚒𝚝-𝚊𝚛𝚎𝚊-𝚋𝚕𝚎𝚎𝚍" but wasn't sold enough on it

Introducing 𝚑𝚒𝚝-𝚊𝚛𝚎𝚊—a collection of @tailwindcss utility classes for expanding the hit area of interactive elements. Small hit areas are a silent UX killer. One class fixes it. Distributed via @shadcn registry - see link below.

@andrii_sherman finally the pnpm error about the old chokidar will disappear

it's time

@jaykch thanks 🤝

@letstri 10/10 clutch setup bro