NODESASS_TRACE: Live tracing facility#1007
Conversation
|
Same output (with sass/libsass#1288 enabled as well): |
|
ping! it merges with the current master :) 7c15014 |
|
This would mean rebuilding the 3.3.0 binaries, so not this time :) |
|
I'd also like to seen some docs how to use this added. I'd like to play with it before shipping it. |
|
I assume this needs sass/libsass#1288 to of any use @saper? |
|
Nope, it has the same implementation though (could be shared maybe). Will work on this, since it has proven already useful e.g. to triage out libsass bugs. |
|
👍 for the when we land libsass@3.3 |
|
Moving this to next.patch milestone. Let's get this sorted. |
saper
force-pushed
the
master
branch
2 times, most recently
from
6c128d9 to
1e4bba8
Compare
|
@xzyfer are you going to manually merge this for 3.7, or bump to the next one? |
|
@saper is this something you still want? |
|
On Fri, 29 Apr 2016, Michael Mifsud wrote:
@saper is this something you still want?
yep.
|
|
Rebase and |
Set NODESASS_TRACE enviroment variable to any value to get lots of output.
Introduce one true way to print contents of the SassValue union.
|
@saper feel free to merge if you're still interested in this :) |
3 participants
Introduce the ultimate libsass C API
troubleshooting tool.
See your JavaScript values being folded
into the libsass context. And back.