Symfony is moving bundler integration from Webpack Encore to Reprise

Symfony’s current documentation now describes Webpack Encore as a legacy, low-maintenance bundler option and recommends Symfony Reprise when a project needs a JavaScript bundler. Reprise provides Symfony-side integration for Vite and Rsbuild. Version 0.8.0, released August 19, adds a per-copy option that preserves stable file paths while putting the content hash in the manifest query string, restoring an Encore behavior some applications, PHP code and CDN rules depend on.

This turns a bundler preference into a migration decision for Symfony teams. Existing Encore applications remain supported, but new bundler work is being directed toward Reprise, and the project now has an explicit migration map from Encore calls. The 0.8 compatibility fix matters because it removes a practical reason some codebases could not migrate without custom build plugins. Reprise is still 0.x and explicitly experimental, so builders gain a modern Vite/Rsbuild path but should not treat it as a drop-in stable replacement yet.

Symfony’s Encore documentation says Encore is in low-maintenance mode, limited to bug fixes, security patches and peer-dependency updates, and recommends migration to Reprise. Reprise does not try to wrap a bundler the way Encore wraps Webpack; it supplies the Symfony-specific pieces around Vite or Rsbuild, including entrypoints and manifest integration, Twig asset tags, dev-server wiring and Symfony UX/Stimulus support.

Encore could copy assets to a stable path and place the version hash in the manifest value rather than the filename. Reprise originally always hashed copied filenames. Version 0.8 adds a `hash` option so applications that hardcode paths, read assets from PHP or rely on stable CDN paths can preserve that behavior while migrating. The same release also fixes a Vite/Rsbuild manifest discrepancy.

Symfony repeatedly labels Reprise experimental and warns its API and behavior may change drastically. Teams should therefore separate the strategic signal—Encore is now the legacy bundler path—from the operational choice to migrate immediately. Existing Encore deployments do not need an emergency rewrite; migrations should be tested against build output, Twig helpers, copied assets, CDN rules, Symfony UX and deployment caches.