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.
Some SCSS files refer to invalid path (a11y)
See original GitHub issueIn 5cf7d175d66120b0e8262bef561f230cb6e31d11 several components got a11y support using a new SCSS resource.
The import is @import '../a11y/_a11y';
Which looks for the file in material/src/lib/a11y/_a11y
a11y is in core
The file exists in material/src/lib/core/a11y/_a11y
I don’t know how the build passed but it’s should be fixed
@import '../core/a11y/_a11y';
The files: src/lib/button/button.scss src/lib/card/card.scss src/lib/dialog/dialog-container.scss src/lib/menu/menu.scss src/lib/select/select.scss src/lib/sidenav/sidenav.scss src/lib/slide-toggle/slide-toggle.scss src/lib/snack-bar/snack-bar-container.scss src/lib/tooltip/tooltip.scss
Issue Analytics
- State:
- Created 7 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
alpha.11-3 is released, should fix this
Oh, I see. Yeah no idea how that ended up compiling. I’ll put in a PR.