-
Notifications
You must be signed in to change notification settings - Fork 381
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
Error: Undefined operation: "1.5 times .875rem" #611
Comments
Closed by #666 |
Still getting this on 3.2.0
Works on 2.3.2 |
Same here:
|
Please provide actual sass code that produces this error so we that we can
reproduce it locally
…On Fri., 23 Mar. 2018, 12:30 am JanikWeb, ***@***.***> wrote:
Same here:
Error: Undefined operation: "2 times 1sqrt(5)/2".Error: Undefined
operation: "2 times 1sqrt(5)/2".
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#611 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWICXNyNxXBVWdoPzv8Cmqo1ZyPiYks5tg6dZgaJpZM4N64SJ>
.
|
@JanikWeb are you using interpolation? Found out that arithmetic doesn't work against interpolated strings. |
@sovanyio does that mean you can't do something like this:
cause I get the same error: Undefined operation: 'rems(18) times 1.25' |
From what I've discovered, it depends on what |
Thank you very much, this was the solution that I needed! @cartbeforehorse |
When doing `npm run build` on one of the projects I am getting an error: > SassError: Undefined operation "-1 * 0.5555555556em". > margin: 0 (-1 * map-get-strict($the-posts, 'gutter')); The problem seems to lie inside the `em() `function which returns interpolated value. The thing is that arithmetics don't perform well when handling interpolated strings. See dlmanning/gulp-sass#611 (comment) ``` @function em($pixels, $context: $browser-context) { @return #{math.div(strip-unit($pixels), strip-unit($context))}em; } ```
I had to downgrade to gulp-sass 3.0.0. It's bug in libsass sass/libsass#2309. So it should solve this by upgrading libsass and node sass to the latest version.
The text was updated successfully, but these errors were encountered: