Overview Tools like Create React App, Vite, etc. use code splitting to improve production app performance. It’s certainly a best practice. For example, when your app is built for prod you’ll see something like this in the final build: main.js chunk-abc123.js chunk-def456.js Problem When netlif…

Apologies if I’m missing something, but I don’t see any problem here. Netlify is behaving as it should. The file has been removed from the deploy - it doesn’t exist anymore, we serve a 404. This is how any server would and should behave. Are you expecting us to continue serving files after they’re d…

@hrishikesh wow, ok! Well: Yes, numerous other services (e.g. AWS Amplify) do retain previous build static artifacts for a period of time precisely to avoid this issue “This is how any server would work.” … Netlify’s use case (unless I’m mistaken) is to be a good way to host an application, not ju…

@dataguy22 In Site deploys overview | Netlify Docs it says No changes go live on your site’s public URL before all changes have been uploaded. Once all the changes are ready, the new version of the site immediately goes live on the CDN. Did you read this and think the old files would still exist…

@dig that mentions nothing about assets from previous builds.

Correct @dataguy22 , it doesn’t say “…all assets from previous deploys are no longer available…” which is obviously what you feel it should say. I get it, some people need very explicit information. What it says is the new assets (new version of the site) are immediately live therefore the old assets…

@dig 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 y…

@dataguy22 You’ve been bitten by the interaction of some complexity (hashed filenames + atomic deploys in this case), and like all developers you’re seeking to avoid it in future. However the answer isn’t necessarily always for someone else to solve it upstream by injecting even more complexity. A…

@nathanmartin I will again reiterate: As I clearly stated, I’m not interested in arguing, I don’t even necessarily disagree with their engineering decision 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…

I can’t answer your main question since you’re seeking an answer explicitly from Netlify and I don’t work for them, but @hrishikesh can speak on their behalf. I do agree that documentation (where possible) shouldn’t lead you to a broken or problematic end result. I’d imagine a note/warning would m…

@dataguy22 you can’t write a post and expect people to not engage in a healthy discussion. Opposing views is not necessarily an argument, so by calling this one, you’re essentially upsetting everyone who decided to chime in this thread. Coming back to the point of retaining previous static build ar…

React app code splitting breaks apps. Solutions?

Support

hrishikesh February 26, 2024, 9:04am 17

The guide is now live here: [Support Guide] Handling code-splitting issues on Netlify

1 Like

Topic		Replies	Views
[Support Guide] Handling code-splitting issues on Netlify Support Guides support-guide	1	1925	February 26, 2024
[Static web generators] - How to handle file-name changes on a new build with atomic deploys Support deployment , gatsby , hugo	19	5549	October 8, 2020
Cache issue on Netlify? Support deployment	42	28823	January 6, 2025
Netlify serve old cached version Support building , deployment , caching	41	7185	March 29, 2022
Skipping CDN file diff Support deployment	33	2414	December 7, 2022

React app code splitting breaks apps. Solutions?

Related topics