When you deploy in production, if an user is navigating the app, the new route files won't match because they have different file names.

[muchisx]

If I have route/a and route/b and I deploy a new version of the app.

An user that's navigating the app and suddenly goes from route/a and to route/b it will experience an error, because the file that was meant for route/b now has changed and the server responds with an error saying the JS asset is not found...

Is this a bug or something there's a solution for already out there?