r/reactjs • • 1h ago

Resource 🗺️ Roadmap to Query v6 · TanStack query · Discussion #12669

Thumbnail
github.com
18 Upvotes

📢 Please don’t get excited, but we’ve started working on TanStack Query v6. We’ll break things, but not too many.

Feedback appreciated 🙏


r/reactjs • • 19h ago

Resource I built NexoreUI: 72 open-source React 19 + Tailwind v4 components, visual builder, templates, and CLI

0 Upvotes

I have been working on NexoreUI for a while now. It started as a personal set of React and Tailwind components, and gradually grew into a small UI toolkit around React 19, Next.js 15, and Tailwind CSS v4.

The main goal was avoiding the usual trade-offs: either a heavy black-box dependency or flashy demos that break in light mode and on 375px screens. Everything uses semantic tokens, supports both themes, respects prefers-reduced-motion, and can be copied directly into your own codebase via CLI instead of living behind an opaque wrapper.

Here is what is live right now:

- 72 MIT-licensed components covering core inputs, tables, tabs, steppers, charts, commerce blocks, media players, and WebGL/canvas experiments, with a Desktop/Tablet/Mobile playground and copy-paste CLI (npx nexoreui add).

- Nexore Make (/nexoremake), a visual drag-and-drop canvas for editing spacing, borders, shadows, and motion and exporting directly to React, Vue, or HTML/CSS.

- Landing Generator (/generator, in beta), a procedural page engine that assembles structured layouts from design tokens and exports clean bundles.

- 40+ page templates (/templates) and a Project/Theme Studio (/create) that configures your palette, radius, and starter CLI setup.

Live site: https://nexoreui.com

Components: https://nexoreui.com/docs/components

GitHub: https://github.com/Al1mov77/NexoreUI

npm: https://www.npmjs.com/package/nexoreui

I just finished a large cleanup pass fixing responsive behavior, keyboard navigation, and snippet completeness across the docs. If anyone tries the CLI, Nexore Make, or the generator and runs into rough edges or accessibility issues, I would appreciate honest feedback.


r/reactjs • • 17h ago

reactques

0 Upvotes

Would React with selective hydration or a framework like Astro be worth considering here? I'm wondering if using React only for the parts that actually need interactivity, while keeping the rest lightweight, could be a good balance for low-end devices. Curious what more experienced developers think about this approach.


r/reactjs • • 18h ago

I built a React + Vue component library with a hosted MCP server so Cursor and Claude Code stop guessing props

0 Upvotes

chould i create a post in there ? with this
I built Orvain UI, a React (and Vue) component library with a hosted MCP server, so Cursor / Claude Code use the real component API instead of hallucinating props.

45 components are free on npm (@orvain/react, no account), there's a Figma library that matches the code 1:1, and theming is one token file.

https://orvain.dev

Happy to answer questions about how the MCP side works.


r/reactjs • • 9h ago

Show /r/reactjs Dinou v10 — an ejectable full-stack React 19 framework (RSC) with zero-boilerplate type-safe routing, 3D caching, and multi-runtime deploy

0 Upvotes

Hi everyone,

I just published Dinou v10.0.2 on npm. Dinou is a full-stack React 19 framework built around native React Server Components (RSC), progressive streaming SSR, and Server Functions.

Version 10 brings a lot of improvements, bug fixes, and a few targeted breaking changes compared to v9.3.0:

  • Truly escaped _ folders: Underscore-prefixed folders (e.g. src/_drafts/) are now completely ignored by the router, bundlers, route typegen, and Server Functions—reserved strictly for WIP drafts, archived routes, or legacy code (while active helper folders like src/components/ don't need an underscore).
  • Per-segment PPR (no parent-to-child inheritance): In v10, ppr is configured strictly per segment rather than inherited down the route tree—so you can have a layout with ppr = true and a child page with ppr = false (each falling back to the global setting in dinou.config.ts).
  • Strict build artifact isolation: Internal server artifacts and build manifests (.dinou/dist1) and pre-rendered SSG/ISR/PPR cache files (.dinou/dist2) are now strictly separated from public static assets (.dinou/dist3, or .dinou/cloudflare/assets on Cloudflare Workers), alongside dedicated platform outputs (.dinou/node, .dinou/netlify/functions, etc.).

For the full list of breaking changes, you can check the docs at dinou.dev—there is both a link to the GitHub CHANGELOG.md and a dedicated v9 to v10 migration guide.

Other notable improvements in v10

Single-pass inline RSC streaming: On initial load or hard reload (for dynamic SSR, PPR resumes, and first-time ISG renders), the RSC payload is now streamed inline alongside the HTML in a single pass. This eliminates a second server round-trip for the RSC payload and avoids hydration mismatches caused by values that change per request (such as Date.now() or random IDs).

Reversible eject & uneject**:** Dinou has always been ejectable via npm run eject, and v10 adds npm run uneject so you can also revert an ejection cleanly and transactionally with a single command.

3D Caching (Horizontal, Vertical, and Temporal): Dinou lets you combine three independent caching axes—Horizontal (decoupled layout and page lifecycles), Vertical (<DinouCacheSlot> component-level Micro-ISR with targeted client refreshSlot()), and Temporal (Partial Prerendering / PPR)—so you aren't forced into an all-or-nothing choice between fully dynamic and fully static rendering.

Zero-boilerplate type-safe routing via "./dinou"**:** Instead of repeating route pattern strings with global "dinou" imports, v10 generates route-contextual "./dinou" modules per directory:

// src/blog/[slug]/page.tsx (Server Component)
import { Link, type PageProps } from "./dinou";

export default async function BlogPost({ params }: PageProps) {
  // params.slug is automatically typed as string
  const post = await fetchPost(params.slug);

  return (
    <article>
      <h1>{post.title}</h1>
      {/* Validated relative link without passing from="..." */}
      <Link href="comments">Comments</Link>
      {/* Dynamic pattern with typed params + auto encoding */}
      <Link href="/blog/[slug]" params={{ slug: post.nextSlug }}>
        Next Post
      </Link>
    </article>
  );
}

Multi-bundler & multi-runtime portability: Dinou v10 continues to strengthen its multi-bundler (esbuild, Rollup, and Webpack) and multi-runtime architecture (Node.js, Bun, Deno, Cloudflare Workers, Netlify Functions v2, standalone native binaries, and pure static SPA export)—so you can deploy pretty much anywhere.

Evolution & AI-agent readiness

Dinou has evolved continuously since its initial release, and v10 is another step toward a rock-solid, modern React 19 framework aligned with current web standards. I recommend staying on the latest version for the best reliability, performance, and feature set.

Dinou is also designed to work smoothly in AI-assisted workflows—coding agents can pick up the framework very quickly. Both the documentation site (dinou.dev, which also exposes /llms.txt and /llms-full.txt), the package README.md (engineered as a compact, single-pass technical spec), and the framework codebase itself (~150 core source files, ~190 total including compiled vendors—whether ejected or in node_modules) are easy for agents to read and reason about.

Feel free to try it out with:

npx create-dinou@latest my-app

Any feedback, questions, or critique is very welcome. Thanks for reading!