-
Notifications
You must be signed in to change notification settings - Fork 1.3k
libsass 3.6 #2685
Comments
https://github.com/sass/libsass/releases/tag/3.6.1 I forked node-sass to integrate the latest libsass 3.6.1 commit #2b8a17a, mocha tests fail, but it does build successfully, and I'm able to use new libsass features like @content arguments. #2714 |
Is adding support for 3.6 anywhere on the roadmap? |
It's a decent amount of work so it'll happen when I have a couple free days
to build the binaries.
…On Thu., 25 Jul. 2019, 11:38 pm Dylan Copeland, ***@***.***> wrote:
Is adding support for 3.6 anywhere on the roadmap?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2685?email_source=notifications&email_token=AAENSWAVZZIS6JUVLOCIJLDQBGUFHA5CNFSM4HSWRSKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ZP4TA#issuecomment-515046988>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAENSWBQE7HWWI2B3ZFTTALQBGUFHANCNFSM4HSWRSKA>
.
|
libsass contains a HIGH severity vulnerability that is fixed in 3.6.0 Can you provide a timeline for the update? |
libsass 3.6.0 also contains a fantastic bug fix sass/libsass#2849 that fixes some Windows specific compilation errors. |
And it implements passing arguments to content blocks, which is super useful. https://sass-lang.com/documentation/at-rules/mixin#passing-arguments-to-content-blocks |
Is there any update on this? |
PR with upgrade is kinda waiting for several months, already ↪️ #2714 |
Does not seem that way to me, sorry! |
|
inspect() function should return an unquoted string when passed a quote string - sass/libsass#2826 This bug has been fixed in LibSass 3.6.0 - unfortunatelly node-sass its having issues updating to 3.6.0 (sass/node-sass#2685) While we wait for node-sass. We need to make sure that values that we pass to the utilities mixins are exactly as described in _system-tokens.scss
inspect() function should return an unquoted string when passed a quote string - sass/libsass#2826 This bug has been fixed in LibSass 3.6.0 - unfortunatelly node-sass its having issues updating to 3.6.0 (sass/node-sass#2685) While we wait for node-sass. We need to make sure that values that we pass to the utilities mixins are exactly as described in _system-tokens.scss
Is this happing any time soon? I'm looking forward to mixin content block arguemnts. |
@karthikrajthandapani this is a volunteer-run project, so no timelines are provided. Sorry. |
This will land in 5.0. follow the open pr for updates.
…On Wed, 30 Oct 2019, 10:48 pm Marcin Cieślak, ***@***.***> wrote:
@karthikrajthandapani <https://github.com/karthikrajthandapani> this is a
volunteer-run project, so no timelines are provided. Sorry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2685?email_source=notifications&email_token=AAENSWGPJZ5UDHS44O7UNXLQRFYALA5CNFSM4HSWRSKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECT3YSI#issuecomment-547863625>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAENSWAVMSIRXWII6LOD6ADQRFYALANCNFSM4HSWRSKA>
.
|
https://github.com/sass/libsass/releases/tag/3.6.0
The text was updated successfully, but these errors were encountered: