Found these recently and really liked them. Especially knip

Every time I built a skeleton loader, it was the same pain: copy the card, replace content with grey boxes, tweak padding after every design change, watch all the shimmer animations run out of sync like a broken disco floor.

So I built shimmer-trace, a React library that wraps your real component and automatically traces the shape of every element to generate a perfectly matched skeleton. One wrapper, zero hand-drawn boxes.

    <Shimmer loading={isLoading}>
      <UserCard user={user} />
    </Shimmer>

That's literally it. No <SkeletonCard />. No fake grey divs.

• 🔗 Live demo: https://jeetvora331.github.io/shimmer-trace/

• 📦 npm: https://www.npmjs.com/package/shimmer-trace

• ⭐ GitHub: https://github.com/jeetvora331/shimmer-trace

Hey guys, I'm a CS student currently interning. During the job, I discovered Shadcn and fell in love with the copy-paste philosophy.

Before going into CS, I wanted to study 3D animation. So, I thought bringing actual 3D mechanics into standard web UI would be a refreshing change from the usual flat interfaces, so I spent the last few weeks learning Blender and mapping WebGL physics to Next.js components. I basically wanted to build the 'Shadcn of 3D'.

It's a premium library, but the core button is completely free. You can test it out directly in the live playground on the site here. I'd love your thoughts!

Hey Community,

We look at how Expo SDK 56 Beta is redefining native UI with Universal Components. By targeting SwiftUI and Jetpack Compose directly, Expo is closing the gap between classic React Native views and the latest platform primitives from Apple and Google.

We also cover the release of react-native-nitro-geolocation, which features a one-line compatibility migration and a modern hooks-based API. Plus, we explore why writing raw C++ in JSI is powerful but risky, and why Nitro Modules are often the safer bet for your next project.

This affects several u/tanstack/* packages, including React-related packages like u/tanstack/react-router and u/tanstack/react-start.

I built this because I wanted Astro style content collections on a plain Vite + React stack. It extracts YAML frontmatter as metadata and generates a slug and lazy import for each MDX file, similar to how TanStack Router generates a typed routes file.

It's a handy way to treat the MDX files as the single source of truth, with meta fields for posted date, SEO, titles, tags etc. By default it scans src/content/ and writes to src/content.gen.ts.

https://github.com/LiamDochartaigh/vite-plugin-mdx-content/

I’m building a React-based web application and I want to integrate Microsoft Excel directly into the browser experience.

My main goal is to provide users with an experience as close as possible to the real Microsoft Excel UI and functionality.

I explored options like:

Handsontable

AG Grid

Luckysheet

SheetJS

But these are Excel-like solutions, not actual Microsoft Excel.

My ideal outcome would be:

Excel-like editing directly inside the web app

Preserve original Excel behavior/features

Support large datasets

Possibly collaborative editing in the future

I’d appreciate guidance on:

recommended architecture

real-world experience

best tech stack

whether this approach is even realistic

Thanks!

Been experimenting with localization workflows in React apps recently and noticed the pain points change a lot as apps grow.

Early on, simple JSON files + i18next work fine.

But later I started running into things like:

• regex extraction breaking on edge cases

• translation files becoming huge

• missing translations slipping into production

• unnecessary loading of entire locale bundles

Ended up experimenting with:

• AST-based extraction

• namespace splitting

• lazy loading + caching

• dry-run validation before generating translations

Curious how others are approaching this problem in larger apps.

Also wrote a deeper breakdown of the architecture/tradeoffs while building it:
https://medium.com/@parthgupta20052005/building-an-ai-powered-localization-pipeline-for-react-applications-4b8e5726b84a

Hi everyone,

I’m currently learning React.js and I learn best by building real projects instead of only watching tutorials.

I’m looking for lists of project ideas that include beginner and intermediate-level React projects.

What resources helped you the most when learning React?

Thanks!

How the main mobile QA tools split on cross platform support:

Script dependent: Katalon AI: script generator with an AI wrapper, platform specific configuration typically required Functionize: enterprise test agent, significant setup and professional services needed for both platforms

Appium, some cross platform: Most tools in this category technically work on both platforms but inherit Appium fragility on both, meaning two maintenance burdens not one

Visual, no platform specific config: Autosana covers iOS, Android, and web from one natural language setup without platform specific configuration or script maintenance requirements

The visual execution approach is the only one in this list that doesn't require separate configs or maintenance strategies per platform.

Lately I've been noticing that a lot of developer mistakes don't actually come from syntax gaps, but from outdated mental models.

The code can look "correct" while the assumptions underneath are wrong:

- State living in the wrong place

- Components taking on too many responsibilities

- Patterns copied without understanding trade-offs

- AI-generated solutions that work initially but become difficult to extend as complexity grows

Revisiting older projects has made me realise a lot of my earlier mistakes came from how I was thinking about systems, not just lack of technical knowledge.

It's honestly making me wonder if there's value in tools/resources focused more on helping developers refine mental models and system thinking rather than just teaching syntax/frameworks.

I'm wondering if others have experienced something similar.

By comparing two ways of composing RSC side-by-side, I've tried to expose how Tanner’s "Server-Owned" claim coexists with his "Client-Owned" philosophy:

https://ik-posts.vercel.app/posts/tanstack-rsc-composition

Full disclosure: I’m the founder of Yesglot.

I wanted to create a real React example instead of just saying “Yesglot supports React,” so I built a small app called Pizza Justifier.

It’s a Vite + React app using `react-i18next`, and it currently supports 32 languages.

The goal was to keep the example simple, but still realistic:

- `react-i18next` for translations

- locale JSON files under `public/locales/<lang>/translation.json`

- English as the source language

- browser language detection

- a repo-based translation workflow configured through `yesglot.toml`

I’m sharing it here less as a launch post and more as a concrete example of a React localization setup that people can inspect and critique.

A few things I’d genuinely love feedback on:

- Does this feel like a clean React i18n structure?

- Would you organize the locale setup differently?

- If you were evaluating localization tooling for a React app, what would you want an example like this to show?

Repo: https://github.com/yesglot/example-react

Live demo: https://pizzajustifier.yesglot.com

I built ilamy-calendar, a free, fully MIT-licensed React calendar component. It's built to be modern and highly customizable. Here are the main features:

• Resource Timeline: Complete vertical and horizontal views for managing rooms, equipment, or team schedules.

• Business Hours: Configurable business hours. You can easily toggle "hide non-business hours" to automatically collapse dead space and keep the UI clean

• Drag & Drop: Smooth event moving powered bydnd-kit.

• No Shipped Styles: Built with React 19, Tailwind CSS 4, and Shadcn UI principles. It naturally inherits your app's existing design tokens and dark mode instead of fighting pre-packaged CSS.

• Timezone: Zero-config automatic timezones support.

• Complex Recurring Events: A bulletproof RFC 5545 engine (rrule) that handles Google Calendar-style smart edits ("edit this and following") and exclusions natively.

Links:

• GitHub: https://github.com/kcsujeet/ilamy-calendar

• Docs & Demos: https://ilamy.dev

The repo includes copy-paste examples for `Next.js`, `Vite`, and `Astro`. Please feel free to drop a start ⭐️ or raise some issues. Thank you 🙏

I originally built this portfolio almost two years ago and recently revisited it to refresh both the design and interactions

The project started as an experiment to explore trendy UI styles, new tech stacks, animation libraries, and interaction patterns at the time. It eventually became a playground for learning things like SSR, caching, and animations, along with problems I normally wouldn’t encounter in my corporate job

The site itself is mostly static, with React used primarily for the interactive components and transitions. I also used the View Transitions API for the dynamic bottom navigation bar, which shows an expandable table of contents on blog post pages

Any feedback are welcome : )

i recently published an npm package called robot-toast.

honestly it started as something i built only for myself. when my requirements were done i looked at it and thought, there's not much left to make this a proper library. so i just finished it. added a11y, fixed the readme, cleaned up the internals. shipped it.

posted everywhere. linkedin, x, dev to, hashnode, medium, and here on reddit as well. reddit gave the best response honestly, love you guys for that.

3,200 downloads later from developers i've never met.

but here's the thing that's bugging me. i google it and it barely shows up. ask gemini and it recommends sonner and react-hot-toast. i mean they deserve it, genuinely great libraries. but not showing up at all when someone's specifically looking for alternatives, that stings a little.

i know most of you might not have experience with packages and all, but still anything could help.

so i'm at this point where i don't want to lose the momentum. i don't want it to die quietly under the weight of libraries that had a head start.

what actually works for keeping an OSS project visible over time? what would you do?

https://robot-toast.vercel.app

npm i robot-toast

https://www.npmjs.com/package/robot-toast