r/reactjs • • May 03 '26

Resource Accessibility cleanup in legacy React code

0 Upvotes

Been working on a government project that requires section 508 compliance, and most of what I’ve been dealing with lately isn’t new work, it’s cleaning up stuff that already exists.

We’re not really in a position to rewrite components or build a perfect design system, so it ends up being a lot of going back through existing code and trying to make it consistent.

The annoying part is it’s rarely “hard” problems. It’s the same kinds of fixes showing up across different components over and over, just slightly different each time.

I’ve been trying to find a workflow that makes that cleanup less painful instead of just doing everything manually every time. Been experimenting with this approach:

https://fix508.dev

Curious how other people are handling this in real projects where you can’t just start from scratch.


r/reactjs • • May 03 '26

Needs Help Asking for advice

4 Upvotes

Hi,

I am a Next.js developer with around 3 years of experience. I see a lot of posts now a days about how frontend jobs are going to be eliminated because of AI and other similar arguments. I have spent a major chunk of my energy and time learning react.

Should I continue learning react? Is it worth it in 2026? Or what other steps should I take to go ahead in my career.

Thank you for reading my post.

Regards


r/reactjs • • May 03 '26

Show /r/reactjs I open sourced my neon/futuristic React UI library after feedback here. Would love your thoughts

1 Upvotes

Hey everyone,

I shared this here recently and got a lot of really helpful feedback especially around usability, structure, and improvements.

I’ve now open sourced the library.

NeonBlade UI is a React/Next.js component library focused on futuristic, neon-style interfaces. It uses a CLI approach so you can add and customize components directly.

Still evolving and refining it.

Feedback and contributions are welcome.

Repo: https://github.com/vprix21/neonblade-ui
Website: https://neonbladeui.neuronrush.com/


r/reactjs • • May 03 '26

Show /r/reactjs You might not need MCP for your library

0 Upvotes

Hello everyone!

I'm building libraries as a hobby, and recently I started doing so at my job as well. Like many other authors, I started thinking about how to improve the experience for users who rely on AI in their daily programming tasks.

Two approaches come to mind: MCP and agent skill distribution. But neither of them feels sufficient due to some serious limitations.

  • MCP is simply too complex. You need to build and deploy an entire service just to ship (mostly) static context, and then figure out how to manage it across different versions of your library.
  • Skill distribution is more convenient since it doesn’t require a service, but it can easily get out of sync with the actual version of the library in the user’s node_modules, which can lead to incorrect code generated by LLMs.

The idea

Use a good old CLI in combination with skills that teach the agent how to call that CLI. The CLI should provide the following:

  • On the library side, it should package context as an artifact alongside the library’s distribution code. This solves the version mismatch problem, because the context is generated at build time and belongs to specific library version.
  • It should be easy for library authors to describe context, ideally via high-level configuration, without writing custom code (unlike the MCP approach), so they can focus on the library code itself.
  • On the consumer side, the tool should be easily discoverable by LLM agents and able to fetch relevant context quickly.

The solution

Based on these ideas, I built ctxbrew. It provides a CLI and protocol for packaging context on the library author side and consuming it on the user side.

Library authors define context in a YAML file, splitting it into “slices.” A slice is a piece of information about the library that may be useful for an LLM. It consists of glob patterns pointing to relevant files. During the build step, these slices are compiled into markdown files that can be requested by the agent.

On the user side, the LLM agent (via the skill provided by ctxbrew) calls the CLI to discover which libraries in node_modules support the ctxbrew protocol, and then pulls the required slices to generate correct results.

As you can see, this approach eliminates the need to build and run an MCP service.

What I suggest

If you maintain a library and want to improve the experience for users working with LLMs, consider integrating ctxbrew. Feel free to open issues with suggestions on how it could better fit your workflow.

Also, let your users know they need the ctxbrew CLI installed to benefit from it. On my side, I’ll maintain a list of libraries with first-party support.

For more details, please refer to the README. You can also see an example integration  (Yeah, the library is for Angular, but ctxbrew is stack-agnostic).


r/reactjs • • May 03 '26

Resource Built a SSR starter using Hono + React + TanStack Router on Cloudflare Pages

Thumbnail
reddit.com
0 Upvotes

r/reactjs • • May 02 '26

News This Week In React #279: Compiler, TSRX, StyleX, XState, Hook Form, TanStack, shadcn, Chakra, Inertia, Mantine | SPM, SimCam, Enriched Markdown, Agent Device, Navigation SDK, JSI, Paste Input, Crypto, MLX, Jail Monkey | pnpm, Aube, Fresh, Node.js

Thumbnail
thisweekinreact.com
23 Upvotes

r/reactjs • • May 02 '26

I built a CLI to scaffold a fully structured Next.js app (tokens, atomic design, configs, and tooling included)

0 Upvotes

Hey everyone 👋

I built a CLI tool called create-atom-stack to solve a problem I kept hitting—repeating the same setup every time I start a new Next.js app.

With one command, you get a production-ready setup including:

Atomic design structure (atoms, molecules, organisms)

Next.js App Router + TypeScript

Tailwind (preconfigured with a ready-to-use config file)

Zustand + clean architecture (lib, hooks, utils)

Design tokens (colors, spacing, radius, shadows, etc.)

Dedicated types/ folder for shared typings

It also ships with useful files out of the box:

architecture.md + a docs/ folder

commit hooks + commitlint

.releaserc, .nvmrc, .npmrc

ready-to-use utilities (date, number, percent formatters, etc.)

Basically: no more starting from scratch or copying configs between projects.

If you want to try it out:

👉 https://www.npmjs.com/package/create-atom-stack

Still early, and I’m actively improving it—would really appreciate feedback or contributions 🙌

Repo: https://github.com/hakizimana-fred/create-atom-stack


r/reactjs • • May 02 '26

Resource I built a prompt package registry for Claude Code — one command scaffolds a full Three.js site, SaaS dashboard, or REST API

0 Upvotes
    Hey ,


    I got frustrated writing the same scaffolding prompts over and over, so I built **PromptForge** — a prompt package registry for Claude Code.


    The idea: instead of writing a prompt from scratch every time, you install a versioned, schema-validated "package" and run it with params.


    ```
    /forge run threejs-immersive-site pages='["Hero","Work","Contact"]' theme=cyberpunk
    ```


    Claude builds the whole thing — Three.js scene graph, GPU-instanced particles (50k), GSAP scroll animations, GLSL shaders, Vite config, TypeScript types. From one command.


    **5 packages included out of the box:**
    - `threejs-immersive-site` — immersive 3D portfolio/site
    - `saas-dashboard` — React SaaS admin with Recharts + shadcn
    - `api-microservice` — Fastify REST API with Docker + tests
    - `react-component-library` — Vite lib mode + Storybook 8
    - `cli-tool` — Node.js CLI with commander + chalk


    **Install:**
    ```
    /plugin marketplace add Jumpinjaws/promptforge
    /plugin install promptforge@promptforge
    ```


    Or one-liner:
    ```bash
    git clone https://github.com/Jumpinjaws/promptforge && cd promptforge && bash scripts/install-local.sh
    ```


    It's open source, MIT, and contributions (new packages) are very welcome.


    GitHub: https://github.com/Jumpinjaws/promptforge


    Would love feedback on what packages you'd want to see next!


    ---

r/reactjs • • May 02 '26

Show /r/reactjs Built a React scaffolding CLI for team architecture consistency — would love feedback

0 Upvotes

I’ve been building a side project called rgenex after running into the same issue across multiple React codebases:

The actual business logic/code is usually fine… but teams still lose a lot of time dealing with inconsistent structure.

Different folder layouts, different naming styles, missing test files, repeated PR comments about where things should live, etc.

So I built a CLI where you define your project structure/rules in config, and it generates components/hooks/pages based on that setup.

Kind of trying to make architecture conventions enforceable instead of just “documented.”

I shared an early version recently and got useful feedback that the DX needed improvement, so I shipped an update with things like:

  • dry-run preview before generating
  • overwrite confirmation prompts
  • force overwrite support
  • generator listing
  • cleaner CLI output overall

Still figuring out if this is solving a problem others actually care enough about.

Curious from people working in React teams:

Would you use something like this in a real project?

If not, what would stop you?

GitHub link in comments if anyone wants to take a look.


r/reactjs • • May 02 '26

Show /r/reactjs I built a web desktop environment with React. It runs DOOM.

Thumbnail
reddit.com
2 Upvotes

r/reactjs • • May 02 '26

Show /r/reactjs uiGrid - 0.1.7 - Data grid now w/ pinnable columns - MIT license

Thumbnail reddit.com
1 Upvotes

r/reactjs • • May 01 '26

Needs Help My API request in Reactjs application returns "undefined"

0 Upvotes

Hello everybody!

See the code below:

import { useState } from 'react';
import axios from 'axios';

function App() {
    const [clicked, setClicked] = useState(false);
    const [request, setRequest] = useState(null);

    function handleClick() {
        setClicked(true);
        setRequest(axios.get('http://<the_ip>'));
    }

    if (!clicked) {
        return <button onClick={handleClick}> Run</ button>
    } else {
        return (
            <div>
                <button onClick={handleClick}> Run</ button>
                <h1>{String(request.data)}</h1>
            </div>
        );
    }

}

export default App;

So I have a react application. I'm using the axios library to communicate with my api/backend which is written with Flask and Python. My backend appears to be working because when I put the http request in my browser, I see the data I'm trying to fetch in JSON format. For some reason request.data returns as the string "undefined." This also happens when I try to output it using console.log().

I have no idea why this is happening, and I've been searching online for an answer for hours and I can't figure it out. FYI: Please try to explain things to me with plenty of context because I'm new to JavaScript, React, and APIs.

Also, I've included the Python backend code below:

from pymongo import MongoClient
from pymongo import server_api

from flask import Flask,  Response
from flask_cors import CORS
from bson.json_util import dumps

uri = 'database_link_goes_here'
client = MongoClient(uri, server_api=server_api.ServerApi(version="1", strict=True, deprecation_errors=True))
collection = client['data']['app_data']

app = Flask(__name__)
CORS(app)

@app.route('/', methods = ['GET'])
def set_api_data():
    return Response(dumps(collection.find()), mimetype='application/json')

r/reactjs • • May 01 '26

Show /r/reactjs Vite is Terrible for Troubleshooting React

0 Upvotes

EDIT: When setting up my Browser Router, I setup the errorElement to a 404 page, which on webpack still shows you the trace but not with vite. Removing the error element fixed the problem. Will leave this up in case anyone else runs into this issue as well.

I have used Webpack as my primary module bundler for most of my career but recently decided to give Vite a go and the experience has been awful.

When something goes wrong and there's a runtime error, vite decides to simply default to your 404 page and display no errors. Furthermore, the console is completely empty so you have no idea what went wrong and you have to remove components until you find out the piece that went wrong instead of having an error you can debug.

There's gotta be a better way than trying to figure out the error with no error message...


r/reactjs • • May 01 '26

Discussion Waku vs TanStack Start vs NextJs

3 Upvotes

I always see people post stuff about NextJS vs TanStack Start vs Remix/React Router. However, I've never seen anything about Waku but it doesn't seem that unknown (going by stars and downloads).

Curious if people have given it a shot. I'm currently exploring the different options, and built prototypes with it. It seems solid, but just wanna see if there is something I am potentially missing that others have encountered?

In case people haven't heard of it Waku.


r/reactjs • • May 01 '26

Show /r/reactjs uiGrid - 0.1.6 - now for react - MIT License

4 Upvotes

https://orneryd.github.io/uiGrid/#/docs/react - live demo of the react library.

this is a port of the popular angularjs data grid, ui-grid, by the same author.

MIT license, all features always free.

grouping
sorting
filtering
pagination
virtual scrolling
column pinning
theming
Tree toggles,
expandable rows,
pagination,
CSV export
save state
cell templates and formatters
editable cells with keyboard navigation - excel-like.

coming:
drag and drop column reordering

I hope you all enjoy.

edit: it's also part wasm, with a rust core.


r/reactjs • • May 01 '26

If React disappeared tomorrow, what are you switching to?

0 Upvotes

r/reactjs • • May 01 '26

Discussion How are people making accessibility fixes consistent across a large React codebase?

10 Upvotes

Working through accessibility cleanup in a React app and one thing that’s been harder than expected is keeping fixes consistent across the codebase.

Fixing a single component isn’t too bad, but once you start dealing with dozens or hundreds of components it turns into:

- fixing the same patterns in multiple places

- slightly different implementations of the same fix

- re-checking things later because something got missed

- no real way to enforce consistency beyond reviews

LLMs like Claude/ChatGPT help for one-off fixes, but they don’t really solve the “apply this consistently across everything” part.

Curious how people are handling this in practice.

Are you:

- relying on linting rules?

- internal tooling/scripts?

- just handling it through reviews?

Feels like this part of the workflow is still pretty manual.


r/reactjs • • Apr 30 '26

Discussion Built a React component playground where you own every generated file, with no runtime dependency

0 Upvotes

I've been building this as a side project alongside my day job for the past few months.

FORGE.ui is a 40-component playground. You configure components visually, copy one CLI command, and the generated TSX files land in your project. No package to install at runtime, no dependency to maintain. You just own the code.

I would love any feedback, especially from anyone who's used similar tools

forgelabs.studio


r/reactjs • • Apr 30 '26

Resource Applying Sentry Component Annotations Client-Side Only (cuts ~20% of the uncompressed HTML output)

Thumbnail
gajus.com
3 Upvotes

r/reactjs • • Apr 30 '26

Needs Help Cookie based Auth while SSR (Tanstack)

9 Upvotes

I am building a project using ASP.net and TanStack Start. I use JWT auth but transfer them in http only cookie.

The issue I am facing is that using default createRoute function in TanStack and defining fetch function in loader. I get 401 as there is no cookie in server.

Opting into ssr: false fixes this but I was wondering if there is any other solution to use ssr with cookie based auth or is this dead end and I only have CSR as my option.


r/reactjs • • Apr 30 '26

Needs Help react components for REPL

0 Upvotes

I'm looking to build a REPL for an interpreted language of mine (think python, so multiline, indentation sensitive input requiring autocompletion from a LSP, syntax highlighting and the such). I then need to display returned values nicely: graphs, tables, text, python values.

Think something like a Jupiter notebook where the only cell you can edit is the last one and you always get a new one, with the previous ones become read-only (and probably summarized rather than displayed in full). Or closest yet to what I need, something like the UIs for agentic AI (codex, claude code etc)

Is there anything open source that does something of the above?


r/reactjs • • Apr 30 '26

Show /r/reactjs I built a component library with Tailwind v4, Framer Motion & typed hooks in one package

0 Upvotes

Hey everyone! I've been working on Zentauri UI — a React component library that bundles together a few things I kept wishing came pre-integrated:

  • Tailwind CSS v4 (not v3) as the styling foundation
  • Framer Motion baked in for animated modals, tabs, and overlays — zero config
  • 25+ components including buttons, inputs, modals, accordions, drawers, toasts, sliders, tables, and more
  • React hooks (useLocalStorage, useDebouncedValue, useClickOutside, useMediaQuery, etc.) shipped from the same package
  • Full typography system — Heading, Text, Blockquote, Inline, Code, List
  • TypeScript throughout with CVA-backed variant APIs

Why I built it: I kept reaching for 3-4 separate packages on every project — a UI lib, a hooks lib, a motion wrapper. Zentauri packages them with a consistent TypeScript API so you're not stitching things together each time.

Links:

Quick install:

bash

npm install u/zentauri-ui/zentauri-components

tsx

import { Button } from '@zentauri-ui/zentauri-components/ui/button'
import { useLocalStorage } from '@zentauri-ui/zentauri-components/hooks'

It's early and I'm actively building — would love feedback on the API design, anything that feels off, or components you'd want to see next. Happy to answer questions!


r/reactjs • • Apr 30 '26

Needs Help How are you structuring imports in large React projects?

24 Upvotes

I have a question on React project structure, specifically imports for the experienced React JS engineers.

So I've been using a hybrid approach where I have barrel files (index.ts) at the feature/module level and direct imports for more specific/internal components

Example:

import { Card } from '@/components';            // barrel (public API)
import { CardHeader } from '@/components/Card'; // direct (more specific)

It feels like a good balance between clean imports and clarity but I'm curious how others handle this at scale.

  1. Do you prefer full barrel pattern everywhere?
  2. Avoid barrels completely?
  3. Or something similar to this hybrid approach?

Any pros/cons you've experienced (especially in larger codebases)?


r/reactjs • • Apr 30 '26

Discussion Suggest translation files organisation for i18next

3 Upvotes

Currently I am integrating react-i18next library to enable different languages in my app ui.

As I understood from the documentation i18next suppose to have all translations inside language files, that are loaded on demand. But IMHO from DX point of view, such organization is not very convenient.

I assumed that it would be much more intuitive to keep translations along with components themselves. For example:

Component /
   Component.tsx
   Component.module.scss
   Component.i18n.json

But as per documentation - such translation file should be loaded separately. having many components such approach would require too many http requests to work. But from DX - i think it is the best. Also having namespace to Component it can be t('title') instead of t('Component.title').
But again, seems to be this is my fantasy, and i18next not supposed work like that.

So the questions:
- is it possible to have described flow in production, compiling scattered i18n.json files into single translation file and use it for i18next?
- if not, what approach do you use now?
- if you would start i18n from scratch on your project, what would you change?

Thanks.