-
Notifications
You must be signed in to change notification settings - Fork 22
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
Pull in Bulma mixins - how? #102
Comments
Also tried with:
And
Idea: I think it would be great to have error messages if the file is not found, so it's easier to debug |
Perhaps the issue is that I am using |
Any solution? |
I'm facing the same issue and like to find a solution. I think its cause Bulma is in SASS and our code is in SCSS I think style-resources module must somehow understand both are kinda the same and include them together to import in both SCSS and SASS Till then my working solution is : <style lang="scss" scoped>
@import 'bulma/sass/utilities/mixins.sass';
@include mobile {
.sidebar-wrapper {
position: static;
}
}
</style> |
Simplest workaround:
|
Unfortunately this has not worked for me. It looks like it finds the file (no errors there) but I still get variable undefined errors as if the file wasn't there at all. The only way I can get some sort of result is to add the sass file under scss array, but then I get sass parsing errors (which makes sense). |
I will take back what I said above. @igolka97 solution works, but you need to watch out because if the file you are importing is also importing other sass files using aliases, the path might not be what you expect. Instead, I imported each individual bulma utility file (eg. mixins.sass, initial-variables.sass) utilities.scss instead of importing _all.scss. |
@igolka97 solution dosn't work for me. For some reason it resets most of my scss overrides to default values. |
I have tried to pull in Bulma mixins like this:
But when I try to use the mixin in my compoonent, like so:
It doesn't work, and I get error:
SassError: no mixin named desktop
The text was updated successfully, but these errors were encountered: