[etdev]

Weird...

I did recently switch to hosting through a Cloudflare Worker, so maybe it's a caching issue. Is it possible you've viewed the site before? If so maybe you have an old version of the index.html file in your browser cache that's linking to the wrong assets.

Either way thanks for reporting — I'll look into it!

[yakubin]

I've tracked down the root cause: I needed to disable two uBlock Filters in order to successfully load the page: Fanboy's Annoyance and Fanboy's Social. It seems that they block some JS related to social buttons (https://japan-dev.com/assets/socialButton.9ddbb1cc.js) and that makes the rest of JS responsible for the rest of the page to not execute (due to a failed request).

Sorry for the false flag.

[etdev]

Oh wow thanks for checking, that's helpful to know.

I should probably restructure things so that one component failing doesn't bring down the whole site if I can...

[3np]

Yes, you definitely should. Adblockers is just one reason why networks requests don't always go through successfully expected.

I also get a sha512 mismatch on the CF script.

(Degrading gracefully so content is readable even without client-side JS is an even better idea but that obv takes more effort to sort out on an existing SPA)

Looking forward to reading your article but my reverse-engineering stops here for now (:

[webmobdev]

Yeah, I still get a blank page. (I hope you don't expect us to disable uBlock Origin to see some social media buttons because that's never happening!).

[jmnicolas]

I'm on Windows, blank page with Firefox and uBlock origin. Works fine on Ms Edge (no ad blocker).

[emptyparadise]

Doesn't load in Safari for me with ad blockers.

[etdev]

Interesting, can you let me know which ad blocker so I can try to reproduce?

[emptyparadise]

I think it's the same social media filters that did it. For reference, I'm using AdGuard on iOS and have the social media button filters on.