Errors from code splitting with Redwood Router (potentially)

Hi All, first of this is going to be a deep an obscure post, so bear with me!

Whats the problem? We have bugsnag enabled on our RW site, and every now and then I see an error related to loading chunks. The bug is incredibly difficult to reproduce, but from looking at the logs, it only happens when trying to navigate with redwood router, and the chunks need to be loaded. A few examples:

Example 1: (chunk is definitely there on the server)

ChunkLoadError Loading chunk 7 failed.
(missing: https://www.tape.sh/static/js/7.e9f522d7.chunk.js) 

Example 2:

SyntaxError Unexpected token '<' 
    https://www.tape.sh/static/js/7.e9f522d7.chunk.js:1:1 

Syntax error, really?

Example 3: (similar to above)

Error Network error: JSON Parse error: Unrecognized token '<' 
    ../../node_modules/apollo-client/bundle.esm.js:63:32 ApolloError

---

Other info that may be relevant

• We are using cloudflare in front of netlify, but I disabled netlify’s asset optimisation for JS because it does the weird thing of moving it into a different path on cloudfront. I want to let cloudflare handle all the caching

I’m not sure if its something that’s happening between cloudflare and netlify, but right now leaning towards RR/Webpack doing something

• The unexpected token < error, I wonder if the server is returning html - but why would it do this and why would it happen so rarely?

• I’m going to try disabling the automatic code splitting on RR, and see if it makes a difference.

---

Redwood version: 0.12

[dac09]

@dthyresson - thank you, this is extremely helpful. I’ll look at trying this out in our staging env today.

[dthyresson]

it receives a 522

Might be worth checking out:

Saw this note on Netlify Community about 522s + Netlify + Cloudflare: https://community.netlify.com/t/522-error-connection-timed-out/8138 …

522 is usually reported via Cloudflare, and if you are seeing it from Cloudflare, the only way you’d get it on a Netlify site is if that site were misconfigured as described in

https://community.netlify.com/t/common-issue-why-isn-t-my-ssl-certificate-provisioning-automatically-with-cloudflare-netlify-are-there-other-problems-with-using-cloudflare-in-front-of-netlify/138