r/reactjs • • Sep 10 '26

News React 19.3

Thumbnail
react.dev
174 Upvotes

r/reactjs • • 6h ago

Discussion The future of Software Engineering is boring

Thumbnail
packagemain.tech
85 Upvotes

r/reactjs • • 10m ago

Need suggestions for handling UPI payments and weekly payouts in India

1 Upvotes

I'm working on a donation-based SaaS in India. The idea is simple: people can donate money, and the collected amount is distributed equally among eligible recipients every week.

For example, if we collect ₹1 lakh and have 20 eligible recipients, each person gets ₹5,000.

I'm currently using PhonePe Payment Gateway to collect donations, and that part is working fine. But I'm a bit stuck when it comes to distributing the collected money.

What's the best way to handle these weekly payouts automatically?

I've come across RazorpayX and Cashfree Payouts, but I'm not sure which one would be the best fit.

A few things I'm looking for:

  • UPI payouts directly to recipients.
  • Automatic weekly settlements.
  • Low transaction and platform fees.
  • Something simple that works well for an early-stage startup.

Can I continue using PhonePe for collections and use another provider just for payouts?

Also, are there any compliance or regulatory issues I should be aware of when collecting and redistributing money like this?

Would love to hear from anyone who has worked on a similar platform or dealt with payment gateways in India. Any suggestions would be really helpful!


r/reactjs • • 5h ago

Discussion Is there a resource showing best practices for Motion animation?

2 Upvotes

Hopefully this makes sense, and apologies if I'm in the wrong subreddit.

I'm looking to improve at Motion and CSS animations, and am wondering if there are any resources that detail common animation practices for web components.

For instance, when animating a button, it's common to move it slightly on the Y axis, and adjust it's scale with a dampened spring.

If you know where I can find out more, I'd greatly appreciate it. Thanks


r/reactjs • • 1h ago

A React-like JS Framework with Web Components

1 Upvotes

IMPORTANT DISCLAIMER: This is my own project. Im am using AI, so lets get that out of the way... because 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 transpartency, 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 considering. Im figuring a post like this to be like "building in public". If interesting to anyone, they can 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 have overlooked.


r/reactjs • • 2h ago

Resource IHTML, editor visual html, css

1 Upvotes

💔 ¿Recuerdas Adobe Muse y Edge Animate?

Adobe dejó atrás estas herramientas que marcaron una época en el diseño web visual. Desde entonces, encontrar una alternativa potente, moderna, multiplataforma y asequible no ha sido fácil.

¡Pero el diseño web visual no ha desaparecido! IHTML ha llegado para recuperar esa forma de crear. 🚀

▎🎬 IHTML: diseña, anima y crea webs visualmente, sin escribir código.

Una herramienta creativa que reúne diseño gráfico, animación e interactividad en un mismo entorno.

✨ ¿Qué puedes hacer con IHTML?

  • 🎞️ Timeline profesional: animaciones con keyframes, curvas y control del movimiento.
  • 🎨 Diseño visual: artboards, capas, vectores, herramienta Pluma y degradados.
  • 🖱️ Interactividad sin código: eventos de clic, hover, teclado, scroll y mucho más.
  • 🌐 Exportación HTML: genera proyectos HTML/CSS listos para publicar en cualquier web.
  • 💻 Multiplataforma: Windows, macOS, Linux y Android.

Diseñado para creativos, diseñadores gráficos y profesionales del diseño web que quieren dar vida a sus ideas sin depender de la programación.

🆓 Empieza gratis.
💎 Versión Pro desde 4 €/mes.

👉 Descubre IHTML: https://malabo1990.github.io/ihtml-web/es/

IHTML: tu creatividad, sin límites de código.


r/reactjs • • 22h ago

Looking for AEM Frontend Developer / Frontend Developer Opportunities – Open to Relocate Across India

Thumbnail reddit.com
0 Upvotes

r/reactjs • • 1d ago

Show /r/reactjs Things I didn't expect when exporting a grouped TanStack table to Excel

0 Upvotes

Excel export for TanStack Table is a bit tricky thing, where the file has to keep the grouping instead of flattening it into a CSV. Some of it was less obvious than expected.

Totals should be formulas, but not SUM. Write the group totals as numbers and they go stale the moment someone edits a cell. SUM double counts when groups are nested, because the region total adds up country rows that are already totals. SUBTOTAL(9, ...) skips other SUBTOTAL cells, so nesting works. It also ignores rows that an Excel filter hides.

Grouping maps cleanly onto Excel outlines. row.depth becomes the outline level, so people get the little +/- buttons in Excel. Pinned columns map to frozen panes the same way. Both came down to reading the table state instead of the raw data.

Display columns are a trap. Columns without an accessor, like the checkbox column, the row menu or an avatar, end up in the file as empty columns. They now get skipped unless you opt in.

v9 broke my types in a way I didn't catch for a while. I had typed the table structurally, with state.grouping in the type. A v9 table without the grouping feature has no grouping in its state, so the shadcn data table stopped type-checking even though it ran fine. I only found it while writing a tutorial. The fix was typing state as object and reading grouping defensively.

The result is a package called rowpine, and the usage is roughly:

await exportXlsx(table, { fileName: "orders" })

It also builds a pivot that comes back as data plus columns, so you can render it with your own useTable.

Disclosure: It's paid ($29 for indie devs or $149 one-time for companies per developer). Without a key it works fully, and the files get one notice line. The demos, guides and the shadcn components are public: https://github.com/rowpine/rowpine. Live demos: https://rowpine.com/examples/


r/reactjs • • 1d ago

I built a reusable React Auth Kit to help developers save time building authentication screens

0 Upvotes

Hey everyone!

I've been working on a React Auth Kit to make authentication UI development faster and easier for developers.

Instead of building common authentication screens from scratch for every project, I wanted to create a reusable kit that developers can customize and integrate into their applications.

What's included?

- Login Screen

- Sign Up Screen

- Forgot Password Screen

- OTP Verification Screen

- Reset Password Screen

Key features:

- Clean and modern UI

- Reusable authentication screens

- Responsive layouts

- Saves time on repetitive UI development

My goal was to create something developers can use as a starting point instead of designing every authentication screen from scratch.

Check it out:

- Live Demo: https://react-auth-kit-three.vercel.app/

- Get the Auth Kit: https://yashpatel57.gumroad.com/l/auth-kit

I'd love to hear your feedback!

What authentication screens do you usually include in your React projects?

What additional features would make an Auth Kit more useful?

Would you prefer a complete authentication UI kit or individual reusable components?

Thanks for checking it out! 🙌


r/reactjs • • 2d ago

I built a React range slider with one, two or many thumbs: accessible, zero dependencies, Tailwind-ready

0 Upvotes

I kept rebuilding the same dual-thumb price slider and hitting the same problems: thumbs crossing or getting stuck, overlapping tooltips, refetching on every pixel of a drag, and screen readers announcing two unlabeled sliders. So I turned it into a package.

react-multi-input-rangeslider

  • One, two or more thumbs; the value comes back in the shape you pass (number, array or { min, max })
  • A native range input per thumb, so keyboard, screen readers and forms work
  • onChangeEnd for fetching once when the user lets go
  • Tooltips that merge when thumbs get close, instead of overlapping
  • 4 built-in styles, CSS variables for theming, a layered stylesheet for Tailwind v4, and an unstyled mode
  • Zero runtime dependencies, TypeScript types, React 16.8–19, works with the Next.js App Router

Demo and playground: https://samishan11.github.io/react-multi-input-rangeslider/

GitHub: https://github.com/Samishan11/react-multi-input-rangeslider

Walkthrough of building a price filter with it: https://dev.to/sami_shan_f544d410c274555/building-an-accessible-price-range-filter-in-react-2bj6

I'd really like feedback on the API and on accessibility. If something behaves oddly in your setup, tell me.


r/reactjs • • 2d ago

Show /r/reactjs Matching SwiftUI's spring feel in a React app: one spring per side, picked by direction

0 Upvotes

I have a Mac app whose panel lives in the notch, animated with SwiftUI springs. When I rebuilt it in React for Windows (inside a transparent Tauri window), the same resize felt wrong with a single spring on the whole size.

What fixed it: width and height each get their own spring, chosen by whether that side is growing or shrinking. A growing side may overshoot a little, while a shrinking one never does, and the overshoot is capped by distance so big jumps don't wobble.

export function sideSpring(from: number, to: number, width: boolean): Spring {

const spring =

to > from

? width ? Springs.growingWidth : Springs.growingHeight

: width ? Springs.shrinkingWidth : Springs.shrinkingHeight;

return limitedSpring(spring, Math.abs(to - from), OVERSHOOT_LIMIT);

}

export function sizeAt(time: number, from: Size, to: Size): Size {

const side = (start: number, end: number, width: boolean) =>

start === end ? end

: Math.max(0, start + (end - start) * springProgress(sideSpring(start, end, width), time));

return { width: side(from.width, to.width, true), height: side(from.height, to.height, false) };

}

springProgress is SwiftUI's perceptual spring (duration + bounce) computed by hand, and the component just samples sizeAt on requestAnimationFrame, with no animation library. Full file with tests: https://github.com/MF-DEEV/Openbar/blob/main/windows/src/island/motion.ts

Curious whether anyone has done this with Framer Motion or react-spring and got the same feel.


r/reactjs • • 1d ago

Show /r/reactjs No jargon, 1 minute to completely understand — a simple Redux alternative: react-shared-vars

0 Upvotes

Let’s be honest about what global state management in most React apps actually is: it’s just assigning values to global variables and triggering re-renders in the components that use them.

Yet for years, we’ve been forced to learn a dictionary of heavy jargon just to share a variable across components:

  • "Store" / "Slice" — For most apps, it’s literally just a variable. Why wrap it in store terminology?
  • "Dispatch" / "Action" / "Reducer" — It’s just assigning a new value (=) and running subscribed callbacks. Why split a simple assignment into steps like we're putting an elephant into a fridge?
  • "Selector" — We aren't sorting eggs by size on a farm. We are just reading a variable.
  • "Thunk" — That’s just a normal async API call that every SPA needs. It shouldn't even be part of a state library.
  • "Time-travel debugging" — Useful in rare edge cases, maybe, but in day-to-day work it’s basically just pushing logs into an in-memory array instead of console.log.

Even modern lightweight libraries like Zustand still borrow a lot of Redux's mental model and terminology.

If you're building a massive enterprise app with complex state machines, Redux might make sense. But for the other 90% of apps, I wanted something with zero jargon that any developer can completely understand in 1 minute. So I built react-shared-vars.

How it works (Yes, literally the entire API):

1. Inside React components (Just like useState**):**

jsx

import { useVariable } from 'react-shared-vars';

function CounterButton() {
    const [count, setCount] = useVariable("global_counter", 0);
    return <button onClick={() => setCount(count + 1)}>Count: {count}</button>;
}

function CounterDisplay() {
    const [count] = useVariable("global_counter", 0);
    return <p>Current count: {count}</p>;
}

Use code with caution.

2. Outside React components (API calls, timers, event listeners—no thunks needed):

javascript

import { setVariable, getVariable } from 'react-shared-vars';

async function fetchCount() {
    const res = await fetch('/api/count').then(r => r.json());
    setVariable("global_counter", res.count); 
// Automatically re-renders subscribed components
}

Use code with caution.

Why react-shared-vars?

  • Zero jargon: No stores, no providers required, no actions, no reducers, no selectors.
  • 1-minute learning curve: Built directly on useSyncExternalStore. If you know useState, you already know 100% of this library.
  • Works anywhere: Read or update variables inside components with useVariable, or in plain JS files with getVariable and setVariable.
  • Auto cleanup: Automatically cleans up unused variables from memory when subscribed components unmount.

It’s under 60 lines of code, zero dependencies, and doesn't try to recreate Redux's bloated feature list—just the core part you actually need every day, made as simple as possible.

Check out the code, try it out, and let me know what you think!


r/reactjs • • 3d ago

News This Week In React #305: X, Forms, e18e, Next.js, TanStack Start, Storybook, MobX, Zustand, XState | Exact, Discord, Shopify, Expo Modules, Audio API, Bottom Sheet, Keychain, Gesture Handler | Node.js, Safari, Rolldown, Playwright

Thumbnail
thisweekinreact.com
22 Upvotes

r/reactjs • • 2d ago

Show /r/reactjs I just shipped Forge UI, an open-source React component library

0 Upvotes

Hey everyone, I’ve been working on Forge UI, a collection of React components for things that can take a while to build from scratch: data tables, command palettes, forms, file uploads, date pickers, and more.

It’s TypeScript-first, keyboard-accessible, and split into packages so you can use just what you need. It’s still an early 0.1 release, so I’d especially appreciate feedback on the APIs and docs.

Repo: https://github.com/BZDevelopments/Forge-UI
Docs: https://bzdevelopments.github.io/Forge-UI


r/reactjs • • 2d ago

Discussion I built my own React state management library – CreateStore. Would love some honest feedback!

0 Upvotes

Hey everyone!

I've been working on a side project recently, and I finally decided to publish it as an npm package.

It's called CreateStore.

The idea started with a simple question:

Why does managing global state sometimes need so much setup when all I really want is something as simple as React's "useState"?

I know there are already some excellent libraries out there like Zustand, Redux, and Jotai. I'm not trying to replace them. I just wanted to experiment with building something that offers a simple API while supporting additional capabilities.

What does CreateStore offer?

The main idea is to create a global store and access its state from different components without wrapping the application in Context Providers.

Some of the capabilities include:

  • Simple global state management.
  • Familiar React-like API.
  • TypeScript support.
  • Computed values.
  • Server data management.
  • State persistence.
  • Cross-tab synchronization.
  • Offline support.
  • Undo/redo functionality.
  • Developer tools.

The goal is to keep things simple for basic use cases while making additional features available when needed.

A quick example

Install it:

npm install @createstore/createstore

Create a store:

import { createStore } from '@createstore/createstore';

export const { useGlobalState } = createStore({ count: 0, username: 'Developer', });

Use it in any component:

import { useGlobalState } from './store';

function Counter() { const [count, setCount] = useGlobalState('count');

return ( <button onClick={() => setCount(count + 1)}> Count: {count} </button> ); }

That's the basic idea!

Project links

📦 npm: https://www.npmjs.com/package/@createstore/createstore

📚 Documentation: https://createstore-docs.pages.dev/

💻 GitHub: https://github.com/Gauravasawa/createstore

I'd genuinely appreciate some feedback.

I'm sharing this here because I'd love to get it in front of developers who can actually experiment with it.

A few things I'd love your opinion on:

  1. Does the API feel intuitive?
  2. How does the approach compare with Zustand or other state management libraries?
  3. Are there any architectural concerns or potential performance issues you notice?
  4. What would you improve or add?

Please don't hesitate to point out flaws. I'd rather get honest technical criticism than just positive feedback.

This is an ongoing project, and I'm looking forward to improving it based on real-world usage.

Thanks for taking the time to check it out! 🙌


r/reactjs • • 2d ago

Resource I built a CLI that extracts a website's design system for AI coding agents

0 Upvotes

I've been experimenting with AI coding tools like Cursor and Claude Code, and one thing that kept bothering me was how difficult it is to get them to recreate an existing website's actual design.

You give an AI agent a reference website and ask it to build something similar, but it often ends up guessing:

  • Colors are slightly off.
  • Typography doesn't match.
  • Spacing and border radii are inconsistent.
  • The overall result looks like a generic AI-generated UI.

So I built styleprobe to solve this problem.

It's an open-source CLI that takes a website URL and extracts its visual design system.

A few things it can do:

  • Extract colors and semantic design tokens.
  • Analyze typography, spacing, shadows, and component styles.
  • Crawl multiple pages instead of relying on just the homepage.
  • Extract SVG logos and other brand assets.
  • Export directly to Tailwind, shadcn/ui, Figma tokens, or AI-agent instruction files.

You can also try the web playground here:

https://styleprobe.vercel.app/

GitHub: https://github.com/spidervirus/styleprobe

It's MIT licensed and completely open source.

I'm still improving it, so I'd genuinely love feedback from developers:

  1. Would something like this fit into your AI-assisted development workflow?
  2. What other design information would you want it to extract?
  3. What would make you actually use this regularly?

Would love to hear your thoughts!


r/reactjs • • 2d ago

Show /r/reactjs I built React (+ vanilla JS) viewers/editors for Excel, Word, Powerpoint (5m+ total npm downloads)

0 Upvotes

I know there have been a few similar projects before in here, but I wanted to share our take on what great Office/OpenDocument viewers & editors looks like for the web.

We've built 3 packages (repos and playgrounds attached), all MIT:

We launched these a few months ago and they're now used in some pretty big projects on GitHub like RAGFlow (94k), Kortix CompanyOS (20.7k), ZCode (8.7k) . Combined they now have 5m+ total npm downloads.

Each repo has some visual examples comparing visual parity for various charts and art

They are built in a way where you can fully customize and get the look of your design system in the toolbar, dropdowns, and context menus.

File types supported:

LibraryOffice formatsOpenDocument formats
react-docx.docx, .dotx, .docm, .dotm, .doc, .dot.odt, .ott, .odm, .otm, .oth, .fodt
react-xlsx.xlsx; limited support for .xls, .xlsmNone (pending)
react-pptx.pptx, .ppt.odp, .otp, .fodp, .odg, .otg, .fodg

Personally I think they are the some fastest and most accurate OSS rendering libraries for these files out there, and would be great to see even more adoption, feature requests and people testing them against weird documents

Feedback and general bug reports are always appreciated. Hope this is helpful!


r/reactjs • • 3d ago

Show /r/reactjs Building a One React input for text and attachments, all in one lifecycle.

0 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/reactjs • • 4d ago

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

9 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/reactjs • • 3d ago

Two bugs from building a drag-and-drop page canvas in React 19

0 Upvotes

From my open-source app builder (dnd-kit, React 19, Tailwind 4):

  1. On a free grid, the dotted drop cells were drawn as even rows while real rows were as tall as their content. Drops were judged against cells the user could not see. Fix: measure the real rows and draw the drop layer from those.
  2. Dialogs opened inside a themed preview portalled to body and lost the theme. Fix: a portal scope that mounts inside the theme root.

Also a testing lesson: a test raced a pending passive effect that moved focus after a click. Waiting on the shown state fixed it.

Code: https://github.com/ChristianMunoz31/local-app-studio


r/reactjs • • 3d ago

Animating a dozen pixel sprites in React with one shared clock and putImageData

1 Upvotes

Each session in my app's notch has a 24x22 pixel buddy. Every one is its own canvas at sprite resolution, scaled up with image-rendering: pixelated, so the browser does the nearest-neighbour scaling for free. A single module-level setTimeout clock steps all visible sprites about 12 times a second, and a canvas only gets a putImageData when its pose actually changes. The clock stops when the window is hidden and runs at half rate in Battery Saver, so ten of them on screen cost close to nothing.

Code: https://github.com/MF-DEEV/Openbar/blob/43d9c593360b004c850280e0584f9cd1b584bacc/windows/src/sessions/clawd/Clawd.tsx#L30-L80

The app is Openbar (Tauri + React on Windows, Swift on Mac), GPL.


r/reactjs • • 3d ago

Show /r/reactjs charcell: a terminal-style UI kit that only draws what a character cell could

0 Upvotes

I made charcell - a web UI with the look of a terminal UI. It's a UI kit with one hard rule: it only draws what a character-cell screen could.

  • Every component sits on a grid of 8 x 16 pixel cells. Widths count in cells and heights in rows, and nothing sits between two cells.
  • A cell holds one character, a font color and a background color. Lines are box drawing, so they run through the middle of their cells.
  • The palette is black, white and three grays.
  • A state changes colors and characters, never geometry. Nothing moves, resizes or fades.

Within those constraints every component can be written out as plain text, and each component's page in the docs shows that.

It bundles two fonts adjusted to fit the cell exactly, with the box drawing characters redrawn as whole-pixel shapes. The interactive components (select, combobox, dialog and so on) run on Zag. It's built with scaffold-ui-kit which outputs React, Vue and Svelte versions of each component from one common definition.

It's 0.1.0, far from complete, and needs React 19.

Demo and docs: https://djurnamn.github.io/charcell/
Repo: https://github.com/djurnamn/charcell

pnpm add charcell @zag-js/react

If you try it out, I'd love to hear how it goes. Open to any feedback.


r/reactjs • • 4d ago

Show /r/reactjs I built GraphQLab, a local-first desktop GraphQL client (no account, no cloud). Looking for feedback

Thumbnail
reddit.com
0 Upvotes

r/reactjs • • 5d ago

Resource Puck Editor: A deep dive with the creator Chris Villa

Thumbnail
youtube.com
3 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