React.lazy causes app to break when new version is deployed

[gearnode]

When deploying new versions of my React application that uses code splitting with React.lazy, users who already have the previous version open in their browsers experience broken functionality. This occurs because:

1. The user loads the application (version A)
2. We deploy a new version (version B) with updated chunks
3. When the user navigates to a route that triggers lazy loading, the app attempts to load a chunk that no longer exists or has a different hash in the new deployment
4. This results in a chunk loading error and breaks the application:

Uncaught (in promise) ChunkLoadError: Loading chunk [chunk-id] failed.
(error: https://us.console.getprobo.com/static/js/[chunk-id].chunk.js)