Repo: https://github.com/coterahq/griddle - demo's linked in the readme.

We've been running data-grids over large parquet backed datasets in prod for quite a while now, and we decided to OS the component for others that might find it useful.

I have been building this for a while and it is finally on npm, so I would rather put it in front of people who will tell me what is wrong with it.

How it works. A development-only Vite plugin stamps source coordinates onto intrinsic JSX during serve. You click the broken element in your browser and it reports the file and line that rendered it. Babel then assembles a narrow slice of context from the clicked component, its imports and related components, and a small local model proposes an exact substring replacement. Not a file rewrite. It has to match a unique existing substring or the patch is rejected.

The part I actually care about is that the model's opinion does not count. After every edit it runs your typecheck, lint, tests and production build, then replays your acceptance scenario in a real Chromium instance. Only if all of that passes does it report VERIFIED. Otherwise it reports BLOCKED, leaves the diff in your working tree so you can read it, and tells you the undo command.

That distinction earned its keep while I was testing. One patch passed typecheck, lint, tests and the production build and was still completely wrong. It set state back to the previous array reference, React bailed out on Object.is, and nothing re-rendered. Four green checks on a broken fix. Only the browser replay caught it.

It also refuses to run if your acceptance scenario already passes against the unmodified app, so it cannot invent a reproduction to look useful.

Everything is local. Qwen 2.5 Coder 1.5B on CPU through node-llama-cpp, which npm installs as a prebuilt binary, so nothing needs to be on your PATH. If you already run Ollama or LM Studio you can point it there instead. No API keys, no telemetry, nothing leaves the machine.

npm install -g @react-surgeon/cli cd your-react-app npm install -D @react-surgeon/vite-plugin react-surgeon init 

Honest limitations, because I would rather say them than have you discover them:

• The 1.5B model solves roughly half the bugs it attempts on my three-bug demo app and refuses the rest instead of guessing. Read every diff.
• Analysis resolves ordinary relative imports. Path aliases, higher order components, re-exports and provider chains are where it will get the context wrong, and that is the next thing I am working on.
• You write the acceptance scenario. There is a command that drafts one from a recorded interaction and tells you which values changed, but you still decide what correct means.

Repo, docs, and a demo app with three reproducible bugs: https://github.com/waleedmustafa971/React-surgeon

MIT licensed.

I am genuinely after criticism on the approach, particularly whether the verification gate is strict enough or whether I am fooling myself with it.

Hi everyone, I'm building a Bitcoin Forensics and AML (Anti-Money Laundering) dashboard that visualizes pre-computed ML classification results and network graphs using React and Cytoscape.js. My backend and core graph logic are fully functional, but I'm struggling to put together a clean, professional dashboard UI layout (sidebars, risk score cards, metrics, alert logs) under a tight deadline. Does anyone know of any open-source dashboard boilerplates, free UI kits, or quick workarounds suitable for data-heavy forensic tools? Any recommendations would be greatly appreciated. Thanks!

Hi everyone! 👋

I’m currently exploring full-time remote opportunities as a Senior React.js Engineer / Frontend Engineer / Tech Lead, and I’m open to working with teams across any time zone.

I have 10+ years of software engineering experience, with a strong focus on React.js, Next.js, TypeScript, JavaScript, and React Native.

A few things that define my experience:

• 🚀 React.js & Next.js — building production-grade applications, reusable component systems, performance-focused UIs, SSG/ISR, and modern frontend architectures.

• 📱 React Native — full ownership from architecture and development all the way to iOS/Android builds, CI/CD, signing, TestFlight/App Store and Google Play releases.

• 🧑‍💻 Strong hands-on ownership — I’ve independently designed and delivered products end-to-end, including working directly with requirements, architecture, development, deployment, and ongoing improvements.

• 🌎 Multiple clients & products — experience working across different client projects and business domains, adapting quickly to new requirements and technologies.

• 👥 Technical leadership — experience leading teams, mentoring developers, conducting interviews, establishing engineering processes, and driving projects from kickoff to delivery.

• 🤝 Client & stakeholder communication — comfortable communicating directly with clients and stakeholders, translating business requirements into practical technical solutions, and working effectively with distributed teams.

• ⚡ Performance & scalability — Core Web Vitals, caching, lazy loading, virtualization, memoization, bundle optimization, and scalable component architecture.

I’ve also worked on enterprise platforms, logistics systems, LLM/RAG applications, content management platforms, and white-label mobile products.

I’m looking for a team where I can stay hands-on technically while also bringing my leadership and ownership experience.

📍 Location: Hyderabad, India
🌍 Preference: Fully Remote
🕐 Timezone: Open to any time zone
💼 Availability: Full-time/ Contract opportunities

LinkedIn: https://linkedin.com/in/anurag-vasi-46595810a

If you’re hiring for a senior React/Next.js/React Native role, or know of a team looking for someone with this background, I’d be happy to connect.

Thanks! 🙌