-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
.vuepress/style.styl does not take effect in the production environment #977
Comments
Could you provide the reproduction repo? |
Thank you for the reply,the repo is https://github.com/xnng/vuepress-test |
Hey, thanks for your repro, this is an issue caused by this commit of webpack-contrib/mini-css-extract-plugin. Fixed and published at |
ulivz
pushed a commit
that referenced
this issue
Nov 13, 2018
This is because mini-css-extract-plugin had a internal change at webpack-contrib/mini-css-extract-plugin#265 which will cause issue to VuePress.
ulivz
added a commit
that referenced
this issue
Nov 13, 2018
This is because mini-css-extract-plugin had a internal change at webpack-contrib/mini-css-extract-plugin#265 which will cause issue to VuePress.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
.vuepress/style.styl can not use in production enviroment,but in development enviroment is available
when I
vuepress
Version
0.14.4
Steps to reproduce
I want to override some of the styles. I created .vuepress/style.styl and it took effect after I
vuepress dev
it, but it didn't take effect after Ivuepress build
it.I tried both on windows and CentOS, and they all had the same effect.
Do I need additional configuration to add this file? I didn't see it in the document.
What is expected?
I hope than
.vuepress/style.styl
can use in dev and prod enviroment。This is my css:
This is dev:
This is prod:
I found a way to solve my problem,add
!important
like this :What is actually happening?
After I build it,
.vuepress/style.styl
didn't work.Other relevant information
The text was updated successfully, but these errors were encountered: