- Yes, software documentation should be very clear and explicit
- There are numerous previous threads asking about this issue; people have even gone out of their way to create open-source plugins to address the problem: Keep .js chunks from old deploys
- No need to argue about it, it’s a waste of your and my time
Whether this behavior is “right” or the “best” is obviously subjective, as are all best practices. Personally, I even probably think it is best practice to have atomic deploys in this manner – but Netlify strives (I think) to be an easy way to deploy robust, reliable applications. So either clearly document these types of gotchas, and/or build ways to allow customers to easily avoid them.
All I’m interested in at this point is determining whether Netlify thinks that the having step by step docs which, if followed to a T, lead to deploying apps that break for end-users.