-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Moving of variables in 0.4 breaks webpack build #708
Comments
same problem, but importing variables first actually worked for me |
Mmmh I'm not sure why it fails. One solution would be to put the variables in |
I'm still getting this error. It's very frustrating tbh. I was going to rant as to why people ship broken software, but I realized bulma is still at 0.4. Nonetheless, I hope someone can fix this. I've been stuck on this on and off for months |
Have you tried #708 (comment) ? |
Getting this error too - is there a known solution ? |
So you want us to modify |
@jeffijoe That's what I did to resolve the issue. It's a sad state of affairs. |
@samayo that's not a viable solution at all; our Docker builds fetches fresh packages every time. I don't understand why this issue was marked closed? |
So I can duplicate the variables in I'll reopen. |
I'm doing: @import '../../sass/variables' // this imports the bulma vars
@import '~bulma/sass/utilities/mixins' And I still get
|
This means, mixins are not imported. Make sure you are importing. I would prefer using |
@samayo my consuming sass file is nested deeply, when reaching into node modules I always use the tilde char. My variables.sass is my own variables that imports bulmas as well. |
@jeffijoe I think I made a mistake. It seems the sass/variables that is no properly imported. I had the same issue and that's how I fixed it. Or try with another tagged release, this fixes the issue 90% of the time. |
@samayo so what exactly did you do to fix the issue long-term? |
Only the tag messed up the issue. I fixed the long-term problem by using another release |
@samayo yeah I am using 0.3.2 because 0.4.x causes this issue. |
I followed @jgthms's advice seems to be working well on my webpack build now |
+1 I followed @jgthms's advice |
Overview of the problem
This is about the Bulma CSS framework
This is a Sass issue
I am sure this issue is not a duplicate
Description
In 0.4, the responsiveness variables were moved out of
mixins.sass
and intovariables.sass
. This breaks my code where I rely on mixins in my own code.I tried doing
But that didn't work either. Error:
Steps to Reproduce
mixins.sass
+tablet
I think if you just add an
@import 'variables'
tomixins.sass
we should be good.This is preventing me from uprading to 0.4.
The text was updated successfully, but these errors were encountered: