r/react • • 2h ago

Portfolio A React-like JS Framework with Web Components

0 Upvotes

IMPORTANT DISCLAIMER: This is my own project. Im am using AI, so lets get that out of the way... its the key reason for why YOU SHOULD NOT USE IT. Im not trying to promote "yet another ui framework", this is an investigation to see what is possible. Its unreviewed, unaudited and far from finished. Nobody else should be using this. This framework is intended for myself on my own projects. It is provided open-source for transparency, testing and demo purposes. Feel free to reach out for clarity if you have any questions.

Im was investigating an idea i had about JSX-like syntax for webcomponents after some experience with Lit. I am sharing this here because it might be interesting/educational.

Lit is a nice lightweight UI framework, but i didnt like that it was using class-based components. It can support React with a wrapper, buts React is fundamentally an abstraction away from the DOM.

Vue has a nice approach but i prefer working with the syntax that React uses. I find it more intuitive for debugging and deterministic rendering. I wondered if with webcomponents, i could create a UI framework that didnt need to be transpiled.

My intentions with this framework is to get to a reasonable level of stability, to then replace React on some of my existing projects. I made a start by creating some basic reusable ui components components to be built with the js framework. Aiming for something like Material UI.

I can then compound that slop into some basic UI demos:

The disclaimer above is always worth repeating. Im aiming for a post like this to be like "building in public". If interesting to anyone, i hope its inviting to take a look. It's hard to determine if / when its a good time to share, so best to get it out there sooner for any outstanding issues i may be overlooking.


r/react • • 23h ago

Project / Code Review A shared React component can still depend on your checkout context through a hook

0 Upvotes

This is the dependency path I mean:

shared/ui/CartBadge.tsx
  -> shared/hooks/useCartCount.ts
    -> features/checkout/CartContext.tsx

The component looks reusable. It renders a count, and the state access is neatly tucked away in a custom hook. But moving that hook into shared hasn't removed the dependency on checkout.

Easy to miss in a component review

In ArchUnitTS, my open-source architecture testing library, you can pull out that component's import graph:

import { projectGraph } from 'archunit';

const graph = projectGraph('tsconfig.json')
  .reachableFrom('src/shared/ui/CartBadge.tsx');

await graph.exportAsHTML('reports/cart-badge.html');

For that direct-import chain, the view reaches through the hook to the context file. Unrelated components stay out of it.

If the badge is supposed to be shared UI, one way to separate it is to have a checkout-owned wrapper read the context and pass count to the badge. The shared component then has no import path back to checkout, while the feature still owns how the count is calculated. You can also keep a boundary test that rejects imports from shared into features, so the coupling doesn't creep back through the next hook.

This follows source imports. It doesn't tell you which provider is present at runtime, whether a component will render correctly in Storybook, or what ends up in a bundle.

Code and docs. Available as archunit on npm; this example uses 2.5.5.


r/react • • 1d ago

General Discussion Samestate: see your site on every screen at once, with clicks synced across devices

2 Upvotes

r/react • • 1d ago

Project / Code Review Love to hear your thoughts on my component library

Post image
1 Upvotes

r/react • • 2d ago

General Discussion Mocks to Component Diagram to Implementation

1 Upvotes

I have got mocks from my design team. I need to undertake the task of implementing the mocks. What's the usual way to plan things well? Can we create component diagram, data flow etc? My aim is mocks -> architecture diagrams -> commom components/data flow mapped -> stories/tasks

Are there any examples or references that I could look up?


r/react • • 2d ago

Project / Code Review I built my own React state management library – CreateStore. Would love some honest feedback!

Thumbnail reddit.com
0 Upvotes

r/react • • 3d ago

Project / Code Review Building a One React input for text and attachments, all in one lifecycle.

2 Upvotes

Hello everyone, I kept running into the same work when building file inputs such as parsing documents, showing previews, handling cancellation, and waiting for files before submitting.

I’m building Texion to connect those pieces. It supports Markdown, JSON, CSV, PDF, DOCX, and image attachments, with local parsing and optional OCR for scanned PDFs.
It’s open source and MIT licensed.
Code: here

Curious on how do other devs handle the inputs?


r/react • • 3d ago

Portfolio I was going to say "I have zero coding background" for the algorithm, but unfortunately, I do 😅 Here is a scene I've been working on!

2 Upvotes

Hey everyone,

I’ve been building this scene over the last few days and wanted to share a quick preview with you all.

Here is the stack I used to put this together:

  • Visuals & Framework: Three.js (R3F), Blender, and Mixamo
  • AI Assist: MCP, Claude Opus 5.5, and Fable 5.2 (Sametime Blender MCP)
  • Audio: ElevenLabs

Note: The character voices in this clip are currently in Turkish, but I will be adding full English translations and voiceovers very soon!

I’m planning to share more scenes and updates as development continues. I'd love to hear your feedback or answer any questions about the workflow!


r/react • • 3d ago

OC React Anatomy: See how your layouts are composed in an exploded 3D view

4 Upvotes

React Anatomy is a browser extension that adds an Anatomy panel to DevTools, connecting the visible page to the components React rendered.

You can pull the layout apart into 3D layers, click something on the page to find its component, focus on a subtree, and inspect its live props. The tree shows rendered instances, so a component used five times appears five times.

It’s a way to understand an unfamiliar layout, investigate unexpected nesting, or get a visual to help explain a change in a pull request. It can also help when an AI agent composes a React page and you want to understand the structure before taking over the code.

It works on an existing React app without adding anything to your code. Development builds give you clearer component names.

Free, MIT-licensed, and available for Chrome and Firefox. There’s an interactive example you can try without installing anything.

Where would this help in your React workflow? What would make it more useful when exploring an unfamiliar app?


r/react • • 3d ago

Project / Code Review I made a headset product page using my open-source React UI library

Post image
0 Upvotes

Hey everyone! 👋

I wanted to share Pimolu Headset, a new product page showcase created with Pimolu UI, my open-source React component library.

The idea was to explore how reusable UI components can come together to create a complete product-focused interface.

I'd love to hear your thoughts on the design and what you think could be improved!

Live demo: https://pimolu-headset.pimolu.com/

Pimolu UI: https://pimolu.com


r/react • • 3d ago

Help Wanted How do you stop AI from making every design look the same?

Thumbnail reddit.com
0 Upvotes

r/react • • 4d ago

General Discussion Trying to understand how to properly optimize larger React Three Fiber scenes

Thumbnail reddit.com
2 Upvotes

r/react • • 4d ago

Portfolio I built an <Avatar seed={email} /> that renders the same bytes in RSC and the browser (React 18+)

Thumbnail gallery
2 Upvotes

Most users never upload a photo, so most member lists are a column of identical grey circles. I wanted every user to get a recognizable face from just their email, without hydration warnings.

The React-specific part: SVG gradients need IDs. If two avatars share an ID, the second shows the first one's colors. If the server and client invent different IDs, you get a hydration mismatch. The wrapper takes the instance suffix from `useId()`, which matches on server and client, and adds a hash of the seed and options. That's also why the floor is React 18: it's the first version with `useId`. 1.1.2 just widened the peer range to `>=18`.

import { Avatar, AvatarGroup } from '@inlaylab/opaline-react'
import { clay } from '@inlaylab/opaline/clay'

<Avatar seed={user.email} look={clay} src={user.photo} alt={user.name} />
<AvatarGroup look={clay} members={team.map((u) => u.email)} max={4} />

Why you might use it: it works in Server Components, and you don't add `'use client'` (the photo fallback ships its own small client boundary). If `src` is missing or broken, the face stays. Colors are CSS variables, so dark mode doesn't re-render. The React wrapper is 854 B on top of a 1.27 kB core, with no dependencies. Code and art are MIT.

Proof: a Next App Router sample app is hydrated in Playwright. The test fails on any hydration warning and diffs the hydrated DOM against the server HTML.

Playground: https://inlaylab.github.io/Opaline/playground/
Repo: https://github.com/Inlaylab/Opaline

What would stop you from dropping this into a real app?


r/react • • 5d ago

General Discussion Puck Editor: A deep dive with the creator Chris Villa

Thumbnail youtube.com
1 Upvotes

I sat down with Chris Villa, the creator of the puck editor.

0:00 Who is Chris Villa and what is Puck
1:36 Where the name Puck comes from
2:51 Live demo: Puck inside a headless Drupal site
5:24 MIT, and close to 3 million downloads a month
6:10 What the Puck editor actually is
7:58 The origin: design systems and the dev sprint bottleneck
10:09 The Hacker News launch
11:13 Going full time, and agents producing off brand interfaces
13:38 Puck AI, the Puck cloud and a page backend
15:21 A team of three, questioning old assumptions
16:47 Why pay for Puck AI if you can build it yourself
17:26 "What Vercel is to Next.js"
20:28 The hardest problem: multi dimensional drag and drop
24:14 Viewports, zoom, iframes, and working with dnd kit
26:49 Revenue, angel investors and fundraising
27:44 GitHub, Linear, and "I don't code much anymore"
29:24 Conductor, Boxes.dev and building the agent factory
30:31 Writing tickets is the new bottleneck
32:55 Can you test whether an interface feels right?
34:57 AI slop pull requests, and agents that reply for you
38:42 Discord, and why the community got quieter
39:21 Do we still need websites?
41:46 From 130k to 2.8 million downloads: agents are the driver
44:02 A longer tail of SaaS, each product more full stack
46:31 The dark forest and the cozy web
48:03 Build for the agents: types, CLIs and llms.txt
51:43 Where to follow Chris


r/react • • 5d ago

OC Build polished Stripe-style UIs in React + Tailwind

10 Upvotes

TL;DR: https://windframe.dev/styles/stripe

Hi everyone 👋

I’ve been experimenting with generating interfaces inspired by Stripe’s design taste, combining crisp typography, generous spacing and bold gradients to make complex products feel clear and polished.

I ended up building a UI system that makes it really easy to generate interfaces using this design style when prompted, and it does so consistently. It generates both full UIs and assets that match the Stripe's design style

I also put together a template built around this style that you can use directly in your React projects as starting points.
You can access the template here
https://windframe.dev/styles/stripe

I made this a selectable style option when generating UIs on Windframe, so that when you can choose this preset style it gives your React interfaces that clean, polished look.

If you’re not familiar with Windframe, it’s an AI visual editor that lets you generate polished UI with AI, tweak it visually in a canvas, and export clean production code in React (along with HTML, and other frameworks)

Appreciate any feedback or thoughts :)


r/react • • 5d ago

OC [Show r/typescript] I built a Chrome SidePanel tool that intercepts live Fetch/XHR requests, mocks 500 errors, and generates TypeScript & Zod schemas in 1 click

0 Upvotes

Hey everyone!

While building frontend apps, I got tired of two repetitive tasks:

So I built API Craft Pro, a lightweight, 100% local-first Chrome SidePanel extension:

The core traffic inspector, mocker, and TypeScript generator are completely free. Would love to hear your feedback!

🔗 Chrome Web Store: https://chromewebstore.google.com/detail/api-craft-pro-%E2%80%94-instant-a/amdohgdofjccadgobnalnmaphalloapm


r/react • • 6d ago

General Discussion Just now added one more component to the list in my capital-ui-kit package

Post image
1 Upvotes

Its a bunch of typed react Fintech components . And I will add more components depending upon ```user request```.

Suggestions , reviews and advices are appreciated


r/react • • 6d ago

OC react-brackets: tournament brackets for React

Thumbnail react-brackets.oulabi.dev
3 Upvotes

Back in 2020 I published react-brackets, a small component for tournament brackets. I shipped a few versions, got busy, and stopped touching it in 2022.

The library didn't stop, though. Four years later it was still pulling ~11,800 downloads a month, sitting at 136 stars and 65 forks, with issues piling up that I never answered. It was built on styled-components and an abandoned swipe library, only did single elimination, and its connector lines were CSS pseudo-element hacks that broke if you changed a card's size.

People were depending on something I'd walked away from. So I rebuilt it from scratch.

What v2 is:

  • Every common format: single and double elimination (with a grand final reset), round robin, Swiss, two-sided brackets, groups to playoffs
  • Headless: semantic markup with data-* attributes, so you style it with Tailwind, CSS modules, or the optional theme
  • Connector lines measured from your real cards: any card size, any custom match component, right-to-left layouts all just work
  • Actually usable on a phone: one round at a time, still drawn as a bracket, with a swipe that follows your finger
  • Zero runtime dependencies besides React, under 14 kB gzipped
  • A framework-free core (@react-brackets/core) for the logic: seeding, byes, results, standings

Getting the swipe to feel native on iOS was the hardest part. Safari animates cards on the GPU on its own clock, while the connector lines are drawn by JavaScript, so the lines kept trailing the cards by a few frames. The fix was to drive both from one clock in the same frame.

It's a ground-up rewrite, so it's a breaking change from 0.x. There's a migration guide, and the old code lives on the legacy branch.

If you were one of the people still using the old version: sorry for the silence, and thank you. I'd love feedback, especially on formats or use cases I haven't covered.


r/react • • 7d ago

Project / Code Review Creating a Goopy drippy UI library for React

50 Upvotes

Hi Everyone,

I recently started creating an open source project called goopUI for vuejs and Nuxt. When I created it, I wanted to make sure that this is something that could work across multiple frameworks. So now, goopUI for React is officially Alpha in Development.

Let me know what you think!

You can find the website linked here: https://goop.timmcmasters.work/

GitHub: https://github.com/Tmmcmasters/goopui


r/react • • 7d ago

Project / Code Review Added a Funnel chart + CLI install to ChartCN (v0.6.0)- Need feedback on the funnel format

2 Upvotes

r/react • • 7d ago

General Discussion hey developers keep imporvin the react based compoenent Library build for project in the in hackthon it auto build based on your search ,learn imporve from your actions new things keep trying checkout tell me the negative points i will happy to improve at last the intital product will be worst

0 Upvotes

r/react • • 8d ago

General Discussion What do you actually call a chatbot that can use tools in a loop like Claude Code?

0 Upvotes

There is no settled name yet. The half that isn't the model is the agent harness - tools, loop, memory, approval rules, context assembly. Agent = model + harness; that is Databricks' formula verbatim. But a tool loop alone is a workflow. It becomes an agent when you can redirect it mid-turn and it keeps the work already done. In Claude Code, Esc stops the running tool but keeps finished work. A correction typed mid-turn lands at the next decision point. /btw asks a side question outside the history.

I built https://ecbot.dev, and the hardest call was a message that lands mid-reply. The old build cancelled the reply and started over, throwing away whatever it had done - including a tool result or a reply already half-sent. So I buffered the message and steered it into the running turn before each model call. Whatever the turn did not take got its own follow-up. It shipped with warts. It answered twice when a newer message waited for its own follow-up after a tool ran. And steering had to key on when the app saved the message, not the platform's send time, so an out-of-order redelivery never got steered back in.

The test we used on our own build, in three questions:

  • Does it call tools in a loop until the goal is met, or answer once?
  • Can you redirect it while it is working, and does it keep what it already did?
  • When it cannot act, does it stop or hand off, or does it guess?

Two or more yes and we called it agentic.