-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
[Bug Report]Invalid CSS after " @content": expected "}", was "($material-light); " #7323
Comments
use |
@DRoet yes,it works after switch sass dependence,BTW,is there any official document show must use sass for 2.0? |
not yet, thats why this issue got tagged with |
@kylejoeckel yes,hope a full upgrade guide after 2.0 release version |
also,it seems no stylus support any more |
That is correct, there is no more stylus support. This is covered in the upgrade guide and will be detailed for the final release. There have been multiple sections added to the documentation where this is explained however: https://next.vuetifyjs.com/en/getting-started/quick-start#webpack-installation As well, the |
using
i think laravel-mix uses node-sass so it must be installed |
I have success to build with this versions {
"devDependencies": {
"fibers": "^4.0.2",
"sass": "^1.25.0",
"sass-loader": "^7.2.0"
}
} took from https://www.npmjs.com/package/sass-loader readme |
This comment has been minimized.
This comment has been minimized.
We kindly ask users to not comment on closed/resolved issues. If you believe that this issue has not been correctly resolved, please create a new issue showing the regression. If you have any additional questions, please reach out to us in our Discord community. |
Versions and Environment
Vuetify: 2.0.0-beta.0
Vue: 2.6.10
Browsers: Chrome 74.0.3729.169
OS: Mac OS 10.14.5
Steps to reproduce
Use
vue create
generate app,then change vuetify to2.0.0 beta.0
,below dependenciesExpected Behavior
Should show a normal index page
Actual Behavior
Show error as below
Reproduction Link
https://codepen.io/tabenren/pen/QRVgpY
The text was updated successfully, but these errors were encountered: