You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 13, 2025. It is now read-only.
Google Chrome Version 62.0.3202.94 (Official Build) (32-bit)
What OS are you using?
Windows 7 64-bit
What are the steps to reproduce the bug?
Create a new Angular CLI project by typing ng new project-name
Install material-components-web by typing npm i material-components-web --save
Change the app's styles.css file extension to .scss, and reference the new name in the angular-cli.json file. Also provide the node_module path to the stylepreprocessor options so it can find components in node_modules/@Material folder at compilation time
Import the sass material-components-web in styles.scss file by using @import "~material-components-web/material-components-web";
Start the app by typing ng s
What is the expected behavior?
material-components-web scss should not output warnings at compile time
What is the actual behavior?
70+ warnings are triggered, which concern mdc.ripple.css and material-components-web.css. Warnings concern Custom property ignored and variable 'var-name' is undefined and used without a fallback
Full warning log can be found here: https://pastebin.com/PTRPWiDt
Any other information you believe would be useful?
For the fallback problem, I found the following pull request that has been merged, but looks like it's still broken: #367
The text was updated successfully, but these errors were encountered:
I'm not an Angular expert but it seems like you're seeing that warning because Angular CLI uses postcss-custom-properties which doesn't support variable declarations on CSS selectors other than :root.
Uh oh!
There was an error while loading. Please reload this page.
What MDC-Web Version are you using?
What browser(s) is this bug affecting?
What OS are you using?
What are the steps to reproduce the bug?
What is the expected behavior?
What is the actual behavior?
Any other information you believe would be useful?
The text was updated successfully, but these errors were encountered: