Missing .css asset on deployed page

[hswolff]

Howdy! Seems the website is missing a .css asset which is causing a broken page.

Currently looks like this:

Let me know how else I can help!

[hhsnopek]

The asset: https://webpack.js.org/acd2001274306f1e8b40.css is not resolving. The hash/filename is updated here: bf53cc0

Note: The missing file is present - gh-pages/acd2001274306f1e8b40.css

[skipjack]

Thanks for alerting us. We are aware of this issue but it's somewhat unavoidable in our current build/deployment process. See the following TODO in #1525:

Consider a better hosting/deployment setup like Netlify (e.g. #845).

It happens occasionally when updates are being deployed. Try the site again -- I just tried and it loaded fine (even after emptying the cache). Sorry I don't have a better answer but we're aware of the issue and are cleaning up the infrastructure supporting the site bit by bit.

Let me know how else I can help!

If someone wanted to dig into a port to netlify, we'd definitely help facilitate.

[hswolff]

No worries, appreciate the followup.

FYI I just tried the site again, including clearing my cache, and still see the same issue.

Perhaps it needs a re-deploy to kick it back into a working state?

[skipjack]

FYI I just tried the site again, including clearing my cache, and still see the same issue.

Hmmm weird, I'll test this out more over the weekend. I'm definitely seeing all 200s in chrome's network tab. Can you try with another browser to make sure it's not a caching issue?

[hswolff]

Just tried Firefox, same thing.

Also co-workers see it at a different internet connection.

FYI this is out of NYC area.

[hswolff]

....and it appears to be working now. Thank you for your patience!

[hhsnopek]

@skipjack https://webpack-js-org.netlify.com/
All that needs to happen is pointing DNS at Netlify and give access to contributors 😄

Edit: An Email invitation has been sent to your Github Profile Email, this will give you admin access to the netlify app itself. This is based on my own fork of the repository. The steps to getting this one up and running is very easy.

[skipjack]

....and it appears to be working now. Thank you for your patience!

Haha yea I think the main issue is that it takes some time for the new content to be distributed through GitHub's CDN or something.

All that needs to happen is pointing DNS at Netlify and give access to contributors...

Awesome, thanks for the email and for setting that up. I'll take a look at it more this weekend and discuss with the other maintainers. Someone had mentioned it previously as a more scalable alternative but I hadn't had time to dig into it.