Reprise 0.8.0, the Symfony bundler integration layer replacing Encore, adds a per-entry hash option so copied files can keep a stable path on disk instead of always being hashed, restoring an Encore behavior some codebases rely on for hardcoded asset paths, PHP file lookups, or CDN rules. It also fixes a manifest key mismatch between Vite and Rsbuild by stripping query strings and fragments from asset URLs before writing manifest keys, so Twig's asset() function resolves consistently across both bundlers. Separately, the project dropped Corepack from its CI in favor of pnpm/setup, following Node.js removing Corepack in v25.
Questions this post answers
How do I make Reprise keep a copied file at a fixed path instead of hashing the filename?
Set hash: false on the copy entry in the Reprise config for Vite or Rsbuild. The file then lands at its logical path, such as public/build/images/logo.svg, and the content hash moves into the manifest.json value as a query string instead of the filename, restoring the behavior Encore's copyFiles() offered by default. Developers migrating Encore projects to Reprise can track bundler config changes like this on daily.dev.
Why does asset() fail to resolve a font file in Twig when using Rsbuild but works fine with Vite?
Rsbuild wrote manifest keys that kept the query string or fragment from CSS url() references, such as build/fonts/query.woff2?v=1, while Vite stripped it to build/fonts/query.woff2. Since asset('fonts/query.woff2') in Twig expects the stripped form, the lookup failed under Rsbuild. Reprise 0.8.0 fixes this by stripping query strings and fragments from Rspack manifest keys before writing them. Teams debugging bundler-specific asset resolution issues can follow fixes like this on daily.dev.
Why did Node.js remove Corepack and what should I use instead to install pnpm in CI?
Node.js stopped shipping Corepack starting in version 25, after its Technical Steering Committee voted to stop distributing it, partly because Corepack was a slow path to pnpm since every command ran through a Node.js shim that had to resolve and download the package manager first. The pnpm/setup GitHub Action fetches the standalone pnpm binary and installs Node.js in one step as a replacement. Developers updating CI pipelines after Corepack's removal can track Node.js tooling changes on daily.dev.