Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
problems with main.css during npm run build since 1.0.12 #602
Is this a bug report?
Have you read the Contributing Guidelines on issues?
(Docusaurus version via
OS : Mac High Sierra
Steps to Reproduce
After update to 1.0.12 and later css would work correctly.
When I deploy my site it does not display correctly, css is broken. In Chrome devtools console I see ```Resource interpreted as Stylesheet but transferred with MIME type test/plain: "https://www.www.www/doc-site/css/main.css"
To demo this..
@dgracehmh It could be something to do with your web server's settings. Docusaurus has been using the latest version and there aren't issues with it.
It would help if you could answer the following questions:
I have a suspicion it is not due to the cssnano change but due to the addition of
My recommendation would be to check your web server configuration that it is serving the CSS files correctly. I had to make this change to the local web server to get it to work - https://github.com/facebook/Docusaurus/pull/566/files#diff-fe37ce87a7b7b83106303bf9233b49fbR508
I'm trying to dig in to figure out what changed since 1.0.11 to break my setup.
The change was that we added doctype to the top of each html file, and that makes browsers less forgiving about non-standard practices. Please check the content type of the CSS file being served. It shouldn't be anything to do with cssnano…
On Thu, Apr 26, 2018, 9:13 AM Darragh Grace ***@***.***> wrote: @yangshun <https://github.com/yangshun> 1. I am using nginx to serve the site on an internal cloud via docker container. 2. Running locally is fine. 3. Sorry, my docs are not online. I've been deploying using exact same config (nginx + docker + Docusaurus) but when I update to 1.0.12 or beyond on the exact same config the css is broken. I'm trying to dig in to figure out what changed since 1.0.11 to break my setup. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#602 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQRHcCZ31q1KLhho7wB_D6m4uqQz-Dzks5tsfI0gaJpZM4Ti_1q> .