-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Mixins may not be defined within control directives or other mixins #339
Comments
Having the same problem here.
|
Hey Guys, thanks for reporting. It's been fixed already and will be released this week. Here's a workaround for the time being #316 (comment). |
Hello, |
Wondering about the status of this fix? The workaround doesn't fix everything for me. after building with [email protected] I get the following => ERROR in ./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/sass-loader/lib/loader.js??ref--8-3!./src/app/@theme/styles/styles.scss Backtrace: |
Hi @jaysturm, please stop posting comments into every closed issue you found related as you are creating a lot of notification's noise for a lot of people. Please consider creating a new one with a description of your setup and reproducible examples. Thanks. |
@nnixaa no problem, I have removed my other comments. So you would like me to create a new issue on something that you are considering fixed? I was simply wondering when your fixes were planned to be released. I will open a new issue, thanks. |
npm i [email protected] this should solve the problem make sure your node version is below 10 |
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior:
Crashes when compiling, with the message:
Expected behavior:
the app should compile
Steps to reproduce:
Not sure here, it happened after messing with the packages organization. I am posting here because it seems like a valid bug, as sass shouldn't allow nested mixins (I'm not an expert, I just read this)
Other information:
Angular, Nebular
Please delete this issue if the nested mixin code is valid indeed.
The text was updated successfully, but these errors were encountered: