Need to handle Sass function references explicitly in the experimental functions feature?

[joelschou]

• NPM version: 6.2.0
• Node version: 10.9.0
• Node Process:
• Node Platform: darwin
• Node architecture: x64
• node-sass version: 4.9.3
• npm node-sass versions: 4.9.3

I'm using sass-extract and have discovered (via Sass Accoutrement) that function references throw errors when .getValue is used on a variable. I put together a proof-of-concept and filed a bug on sass-extract, but the more I poke around and think about what I've encountered, the more this feels like something node-sass (or LibSass) could handle more elegantly. The PoC documents the specific error thrown by sass-extract, but even when I add some handling to that library for a type of SassError, I get different errors coming from the C-API, which points at node-sass. I've had to pull sass-extract from my project as a result—which isn't your concern, of course, but I thought this might be an opportunity to improve the underlying libraries.

[saper]

Would there be possible to have a PoC using node-sass or libsass only?

Btw. I didn't know that something like sass-extract existed, maybe it would be way easier if that were to become a feature of libsass really ...

[joelschou]

I can put one of those together, yes.

Fortunately, we moved away from this specific combination of tools so the problem is no longer giving us headaches, but being able to dump variable values at compile-time still seems like a useful thing to do. It does seem like libsass would have everything available in-memory somewhere, but that's a pretty naïve guess on my part.