You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But this is not true for Windows, where it is a sass.bat. Effectively it results in a re-download of the Sass distributive for each build due to this logic:
The current implementation of the construction of the path for Sass binary relies on the expectation that the main entry point is always named
sass
:sass-bundle/src/SassBinary.php
Lines 162 to 165 in aa47da8
But this is not true for Windows, where it is a
sass.bat
. Effectively it results in a re-download of the Sass distributive for each build due to this logic:sass-bundle/src/SassBinary.php
Lines 37 to 40 in aa47da8
Correct implementation of the
getDefaultBinaryPath
method would be:There is also one more related and Windows-specific issue:
Normally after download bundle tests that download results in the appearance of the Sass binary and throws an exception if it is not so:
sass-bundle/src/SassBinary.php
Lines 109 to 112 in aa47da8
However, for Windows, no such check is applied because there is a separate branch for archive extraction that ends with unconditional
return
.sass-bundle/src/SassBinary.php
Lines 87 to 97 in aa47da8
Because of this, in case if Sass binary download will not cause the Sass compiler to actually appear in the filesystem it will not be reported.
The text was updated successfully, but these errors were encountered: