Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://webpack.js.org/ sends wrong .css file. #1526

Closed
webpack-bot opened this issue Aug 14, 2017 · 1 comment

Comments

@webpack-bot
Copy link

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

The css file for https://webpack.js.org/ is missing.

If the current behavior is a bug, please provide the steps to reproduce.

Open https://webpack.js.org/ in the browser. Also with a hard reload the css file can not be found.

bildschirmfoto 2017-08-14 um 17 44 35

What is the expected behavior?

The browser loads the css file and the website displays correctly.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

  • Browser: Google Chrome 59.0.3071.115
  • OS: mac OS Sierra 10.12.5

This issue was moved from webpack/webpack#5513 by @sokra. Orginal issue was by @phiilu.

@skipjack
Copy link
Collaborator

Yeah this is the same thing that's happens every once in a while when a few deployments are triggered close together. From my understanding, there's not too much we can do about it at the moment with our gh-pages setup. I have a task in #1525 about porting the site to Netlify which @bebraw has said is much more flexible and could resolve the issue. I'll note this over there as well mentioning that Netlify may be a fix as this has come up somewhat regularly.

As with the other times, it seems the CSS file 404s for about an hour at most, usually less, and then the start returning again. Unfortunately, there's not really a "golden time" for merges/deploys as we have users from all over the world but hopefully we can start addressing some of these infrastructure things this soon, as we're much of the way through our content issues.

TLDR; See #1525

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants