Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Investigate StackBlitz issue compiling Sass #2212

Open
trimox opened this issue Apr 16, 2020 · 7 comments
Open

Investigate StackBlitz issue compiling Sass #2212

trimox opened this issue Apr 16, 2020 · 7 comments

Comments

@trimox
Copy link
Owner

trimox commented Apr 16, 2020

Appears StackBlitz template(s) are not recognizing @use as valid Sass rule. Maybe time to look @ alternatives..

StackBlitz template (using canary): https://stackblitz.com/edit/angular-mdc

@RikEskes
Copy link

Could this perhaps be related to #2189 ?

@trimox
Copy link
Owner Author

trimox commented Apr 17, 2020

@RikEskes Yep, both are related issue. Does your StackBlitz ever finish compiling and starting dev server?

image

@RikEskes
Copy link

The StackBlitz used to finish compiling. If it continues not to do so I will create a new one to ensure the issue is reproducible.

@trimox
Copy link
Owner Author

trimox commented Apr 17, 2020

Wondering if enabling Ivy on StackBlitz is causing infinite compilation. Same thing occurs with https://stackblitz.com/edit/angular-mdc

@trimox
Copy link
Owner Author

trimox commented Apr 17, 2020

Hrmm. Not sure this is an @use issue since import fails as well. Maybe something with the approach used inside angular.json's stylePreprocessorOptions to help Sass compiler locate the MDC Web Sass files?

"stylePreprocessorOptions": {
              "includePaths": [
                "node_modules/"
              ]
            },

@trimox trimox changed the title Investigate StackBlitz issue with @use Investigate StackBlitz issue compiling Sass Apr 17, 2020
@RikEskes
Copy link

RikEskes commented Apr 17, 2020

I created a new StackBlitz project which does finish compiling:
https://stackblitz.com/edit/angular-mdc-agnnan

@guillaumegarcia13
Copy link

guillaumegarcia13 commented Aug 12, 2020

I noticed that in your example, @RikEskes, you have commented out the following:

// // Angular MDC
// @use '@angular-mdc/theme/material';

Any reason for doing so? (this is the oppposite of the Getting Started section)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants