question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug Report]Invalid CSS after " @content": expected "}", was "($material-light); "

See original GitHub issue

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 to 2.0.0 beta.0,below dependencies

    "core-js": "^2.6.5",
    "node-sass": "^4.12.0",
    "sass-loader": "^7.1.0",
    "vue": "^2.6.10",
    "vuetify": "^v2.0.0-beta.0"

Expected Behavior

Should show a normal index page

Actual Behavior

Show error as below

 INFO  Starting development server...
 98% after emitting CopyPlugin                                                    

 ERROR  Failed to compile with 88 errors                                                                                                                                                          4:08:53 PM

 error  in ./node_modules/vuetify/src/components/VResponsive/VResponsive.sass

Module build failed (from ./node_modules/sass-loader/lib/loader.js):

    @content($material-light)
   ^
      Invalid CSS after "    @content": expected "}", was "($material-light); "
      in /Users/tam/Work/TEST/my-app/node_modules/vuetify/src/styles/tools/_theme.sass (line 3, column 5)

 @ ./node_modules/vuetify/src/components/VResponsive/VResponsive.sass 4:14-209 14:3-18:5 15:22-217
 @ ./node_modules/vuetify/lib/components/VResponsive/VResponsive.js
 @ ./node_modules/vuetify/lib/components/VResponsive/index.js
 @ ./node_modules/vuetify/lib/components/index.js
 @ ./node_modules/vuetify/lib/index.js
 @ ./src/App.vue
 @ ./src/main.js
 @ multi (webpack)-dev-server/client?http://10.22.11.64:8080/sockjs-node (webpack)/hot/dev-server.js ./src/main.js

.......

Reproduction Link

https://codepen.io/tabenren/pen/QRVgpY

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:11 (5 by maintainers)

github_iconTop GitHub Comments

67reactions
DRoetcommented, May 29, 2019

use sass instead of node-sass for 2.0

3reactions
VRuzhentsovcommented, Feb 13, 2020

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Invalid CSS after " @content": expected "}", was "($material-light)
This is because you need to use sass instead of node-sass . Remove node-sass and use sass instead and this error should go...
Read more >
Frequently asked questions — Vuetify
Vuetify is a Material Design component framework for Vue.js. ... Invalid CSS after @content: expected “}”, was “($material-light);”.
Read more >
"Error: Invalid CSS after" while compiling theme - Drupal
Problem /Motivation When trying to compile the theme, custom droopler_theme gives error. Please note that compiling breaks/stops.
Read more >
media - CSS: Cascading Style Sheets - MDN Web Docs
The @media CSS at-rule can be used to apply part of a style sheet based on the result of one or more media...
Read more >
sass error invalid css after @content expected was ... - 掘金
sass error invalid css after @content expected was ($material-light)技术、学习、经验文章掘金开发者社区搜索结果。掘金是一个帮助开发者成长的社区,sass error ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found