Question about deprecation warnings
See original GitHub issueIs my understanding correct that previous to ~v1.32 Sass wasn’t logging deprecation warnings to stderr? I’m finding that the JS API is not programmatic enough for my needs because from what I can tell, there’s not programmatic way to silence deprecation warnings using the JS API. I’m aware I can use --quiet
as a flag for the CLI, but I need programmatic control over stdout / stderr, which is why I’m using the JS API in the first place.
Assuming my understanding is correct, that forced deprecation warnings are recent and a side-effect of using the JS API, would you recommend I revert my version to ~v1.32 or is there some reasonable way I can suppress the deprecation warnings without resorting to creating child processes and invoking the CLI API instead.
Thank you.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
No, but for the
@-moz-document
deprecation, you can avoid the warning by just interpolating the name.Thanks, there is no warning in the next code:
It seems to be suitable as a temporary solution.