Weave Code
Ux React Laravel Package
symfony/ux-react
Official Symfony UX React integration lets you render React components directly from Twig, pass props, and mount interactive UI inside Symfony pages. It pairs with Webpack Encore for asset building, making React easy to add to traditional server-rendered Symfony applications.
Integration of React in Symfony
Frequently asked questions about Ux React
- Is symfony/ux-react a Laravel package?
- No. symfony/ux-react is the official Symfony UX integration for React, and it is built for the Symfony stack rather than Laravel. It ships no Laravel service provider, facade, Blade directives, or Vite/Mix integration. Its architecture assumes AssetMapper, StimulusBundle, and Twig.
- Can I use symfony/ux-react in a Laravel application?
- Composer installation is mechanically possible because the package is PHP 8.x compatible, but functional use is not. Rendering React components through it requires symfony/asset-mapper, symfony/stimulus-bundle, and Twig, none of which are native to Laravel. You would need to write and maintain a bespoke Twig bridge or AssetMapper shim, which turns a drop-in package into a custom integration project.
- What does symfony/ux-react actually do?
- It lets you render React components directly from Twig templates, pass props into them, and mount interactive UI inside server-rendered Symfony pages. It pairs with Webpack Encore or AssetMapper for asset building. The goal is to add React incrementally to a traditional Symfony application rather than replacing the whole frontend.
- How do I install symfony/ux-react?
- You install it with Composer using composer require symfony/ux-react, then wire it up through Symfony Flex recipes. You also need symfony/asset-mapper, symfony/stimulus-bundle, Twig, and a JavaScript build step such as Webpack Encore. The package will not work standalone without those Symfony components.
- Which Laravel versions does symfony/ux-react support?
- None. The package targets Symfony 3.x minor branches and does not declare support for any Laravel version. There is no Laravel service provider, no config file published to config/, and no Blade or Livewire integration. Treat any claim of Laravel support as inaccurate.
- What should Laravel developers use instead of symfony/ux-react?
- The idiomatic Laravel path to React is Vite with laravel-vite-plugin, optionally paired with Inertia.js for page-level routing. For reactive server-driven UI without a full SPA, Livewire is the standard choice. A plain Vite React entrypoint mounted from Blade is the lowest-glue option if you only need isolated interactive widgets.
- Why does Composer refuse to install or downgrade symfony/ux-react 3.6.0?
- Version 3.6.0 added an explicit conflict against symfony/asset-mapper 8.2 and later. If your lockfile already pins asset-mapper 8.2 or newer, Composer will either block the install or force a downgrade of asset-mapper. This is the only change in the release with dependency-resolution consequences, and it fails at composer install rather than at runtime.
- Does symfony/ux-react work with Laravel Vite or Laravel Mix?
- No. The package integrates with Symfony's AssetMapper and StimulusBundle for asset resolution and controller registration. It has no awareness of laravel-vite-plugin, the Vite manifest, or Laravel Mix. Trying to co-host both asset pipelines in one application is not recommended.
- Is symfony/ux-react actively maintained?
- Yes, it is part of the official Symfony UX family and receives regular releases on the 3.x branch. Maintenance follows Symfony's release cycle, so check which Symfony minor branch your target version maps to and whether that branch still receives security fixes. The asset-mapper 8.2 conflict in 3.6.0 is worth tracking to see if it is lifted in a later 3.6.x patch.
- What are the production risks of adopting symfony/ux-react in a Laravel codebase?
- The main risk is running two parallel frontend toolchains, because AssetMapper plus Stimulus plus Twig would sit alongside Vite and Blade. That increases build complexity, dependency drift, and the surface area your team must own. The asset-mapper version conflict can also block CI at composer install time. Isolation, such as running the Symfony UX surface as a separate service or pre-built bundle consumed over HTTP, is safer than embedding it in the Laravel runtime.
Weaver
How can I help you explore Laravel packages today?