Post cloudfront invalidation some random chunks for certain pages is still pointing to the cached 1
Unanswered
West African Lion posted this in #help-forum
West African LionOP
After invalidating AWS CloudFront, it appears that certain pages on my Next.js 13.4 website are still referencing the browser cached version instead of the latest CloudFront chunk causing that page to crash. How can I ensure that, post-deployment, the website always refers to the latest CloudFront chunk and not the locally cached page chunk?