Sergii Yarochevskyi 🇺🇦

petite-nuxt version? 😀

Why @nativescript.bsky.social doesn't have a similar solution to @shadcn.com components in #nativescript, same building blocks that rely on <GridLayout> and other ns components?

Or maybe there is some solution i havent heard of?

@elysiajs.com paired with @drizzle.team ORM offers unmatched end-to-end type safety.

Use drizzle-typebox to convert Drizzle schemas directly into Elysia validation models. This single step handles type validation and auto-generates your OpenAPI schema seamlessly.
#webdev #typescript #typebox #js

Skip #Electron. Use #Wails (Go) + Your frontend framework of choice.

Wails leverages the native OS webview instead of bundling Chromium.

The result is ~15MB binaries and ~10MB baseline memory usage. It delivers a vastly superior, lightweight experience for users.
#desktopapps #nativedev #webdev

Join the discussion and lets shape the future of cunstomer feedback and apps communities together

#saas #BuildInPublic #CustomerService #indiedev #indiehackers #webdev #developer #shipping #microsaas #solopreneur #bootstrapped

If you want a tool that builds a community instead of just collecting tickets, join the waitlist.

Let’s make feedback feel alive again.

🔗 welcome.feedbacktor.app

#buildinpublic
#indiehackers
#saas #webdev #shipping

I am launching in a few weeks and squashing the final bugs. 🚀

I want to build this WITH you. When you use tools like Canny or Upvoty, what frustrates you the most?
Drop a reply 👇

It’s not just about upvotes. • Open Discussions & Polls. • Help Center / Knowledge Base. • Hidden Posts: Create VIP threads for top contributors. • Staff Banners: Show users you are actively reviewing a thread right now.

I was also sick of duct-taping tools together (Email + Chat + Feedback).

We built the Anti-Silo Inbox. ⚡️ It pulls everything—Support Emails, Live Chats, Feature Requests, and internal team notes—into ONE speed-focused dashboard.
Stop tab-switching.

So I focused on Presence.

Feedbacktor has a live Activity Monitor. • Users see when staff is ONLINE. 🟢 • They see who else is viewing posts. • They see reactions bumping in real-time.
It changes the psychology from "filing a ticket" to "joining a discussion."

You know the vibe of most feedback boards: • A dozen posts from a year ago. • "Status: Under Review" (forever). • Zero engagement.
It feels like a suggestion box in a dark corner. Users drop an idea and leave because it feels dead.
I wanted a town hall, not a graveyard.

I am building another Customer Feedback app. 🚩 (Yes, I know).
"Just what the market needs. Another clone to throw on the pile."

I honestly didn't want to build this. But every tool I tried for my other apps felt like a cemetery. 🪦

Here is why I’m building Feedbacktor 🧵👇

Finally finalized my perfect stack:

◌ index.html
◌ Tailwind CSS (CDN)
◌ Petite-Vue (CDN)

Zero build steps. Instant feedback.

Ok, im kidding but this thing is pretty powerful for simple landings.. And loading time is... fast

#frontend #dx #javascript #vue

You just ned to make sure you run you app dev in bun runtime, by explicitly "bun --bun dev"

The best code is the code (and dependencies) you don't have to maintain.
#bunjs #webdev #backend #fullstack #javascript

I've been slowly ripping out specific DB and Cache SDKs in favor of Bun native drivers.

Before Node.js mindset:
❌ pg (Heavy)
❌ redis (Bloated abstractions)

After Bun mindset:
✅ bun:sql (Native Postgres support)
✅ bun:redis

It shifts validation from "code review" to "instant terminal feedback."

If you want to enforce specific patterns (like strict inputs or design tokens) without killing your dev server performance, check out the Oxc ecosystem.

I implemented two custom JS plugins to harden the codebase:

Backend: Banned getQuery. Forces getValidatedQuery so I can't skip Zod schemas.

UI: Banned raw bg-white. Forces semantic bg-background tokens for proper theming.

I switched my architectural rules to Oxlint and the speed difference is actually insane.

Oxc is Rust-based. I can scan my whole Nuxt repo in milliseconds.

It lets me "spam" the lint command like a quick sanity check while I code without breaking flow. 🧵

I love NixPacks by @railway.com

It was able to easily built the correct dockerimage for my
@nuxt.com app with bun, which i had hard time building with my own Dockerfile

Will this make us all as skilled as @antfu.me 😂😂

Be honest.

When you open the vault:

[ ] Rewrite (I hate myself)
[ ] Ship the legacy trash

Hot take: If you are refactoring a project that has $0 MRR just because a new version of Tailwind came out, you're a digital hoarder rearranging furniture in a burning house.🔥🔥🔥

The dilemma is real.

• Option A: Stick to the spaghetti code you wrote 2 years ago. It’s ugly, but it compiles.

• Option B: Refactor with that new state management library you learned last week.

One ships product. The other ships dopamine.

Here is the cycle:

- Revive old project.

- See it's written in [Old Framework].

- "I should just quickly migrate this to [New Shiny Thing] for better performance."

- Spend 3 weeks configuring the linter, applying new auth library, replacing old sdks.

Project dies (again).

Opening a side project repo after 6 months away is like returning to a crime scene where you are both the detective and the murderer. 🕵️‍♂️💀

The urge to rm -rf and rewrite everything in the latest stack is overwhelming. 🧵

Feels relatable?

On Cloud 9.0 😶‍🌫️
Release details ⇣

Yeah, many of those IDEs don't support some extensions. And also edgy features like swapping eslint for oxlint or using tsgo are not supported yet as well in some. So they will always lag behind

i assume they've sprinkled it with ai nowdays

The future looks bright 👍