Dismiss
  • Scroll up
  • Toggle Theme
  • View as Mobile

persist-previous-build-assets

persist-previous-build-assets copies previous build artifacts into the latest deployment so users with older HTML do not hit missing hashed JavaScript or CSS chunks.

It targets a practical production failure mode: a new deploy ships, old chunk URLs disappear, and active users see chunk-loading errors.

Why it matters

Reliability work is often small glue code around the edges of deployment. Preserving previous assets gives frontend applications a safer deploy path without requiring a larger infrastructure rewrite.