Laravel Laravel Package

Product Decisions This Supports

• Rendering architecture: Informs the build-vs-buy call between server-rendered React components driven from Laravel versus an SPA-plus-API split or a Livewire/Blade approach. This package makes the RSC model viable without a separate Node service.
• Gated experiences as a first-class feature: Rsc::refuse(), added in v0.15.5, lets a server component decline to render its normal branch and hand structured data back to the page. That turns "you can't have this / it isn't ready" into a designed UI state with context, rather than a thrown exception, a redirect, or an empty screen.
• Roadmap unblocking: Supports a roadmap of graceful degradation and progressive enhancement — partial-failure dashboards, soft paywalls, permission walls, onboarding checkpoints, and preview modes that all need a distinct alternate state with data attached.
• Use case fit: Internal admin consoles, authenticated dashboards, multi-step flows, and any page with meaningful "authorized vs. not authorized" or "ready vs. not ready" branches.
• Buy over build: The integration plumbing (component boundary, serialization, server/client handoff) is the undifferentiated part; buy it and spend engineering on product surfaces instead.

When to Consider This Package

Adopt when:

• Your frontend is React and you want Laravel to remain the backend of record, without maintaining a parallel API layer for every page.
• You specifically need data-carrying alternate states — the refusal pattern is the differentiator here, not generic SSR.
• You can pin versions and absorb occasional API movement; 0.15.x signals active development, not a frozen contract.
• You have a small, senior team comfortable reading the package source when docs lag.

Look elsewhere when:

• You need API stability, LTS guarantees, or a deprecation policy before committing — a 0.x minor bump is not a stability promise.
• Your team is Vue, Livewire, or Blade-first; the RSC mental model won't repay its cost.
• You require vendor SLAs, a documented security posture, or a broad plugin ecosystem — verify maintenance cadence and bus factor first.
• The alternate-state need is shallow enough that a 403 page and a flash message already cover it.

How to Pitch It (Stakeholders)

To executives: This package lets us render React pages from Laravel on the server, so one codebase and one deploy cover both frontend and backend. The latest release adds a "refuse with data" primitive: when a user can't see something, a page can decline and return the reason plus whatever the UI needs to explain it. That directly lowers the cost of building permission walls, paywalls, and onboarding gates we currently hand-roll per feature — the same work, once, instead of N times.

To engineering: It's an RSC integration for Laravel. Rsc::refuse() is a control-flow primitive that is neither an exception nor a redirect — the server component short-circuits with a typed payload for the page to render. Recommended posture: pin the version, wrap it behind a thin internal adapter so we own the seam, and treat 0.x as pre-stable. That gives us the capability now without coupling product code to upstream churn.