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
The bug is a minor one, but when resolving node-sass through actions under Bazel, the build folder that is created during the post install process has files with SHAs in them. That means that installs are not a cache hit because it changes between resolutions. The fix for this is just to have node-sass cleanup after itself on postinstall such that it removes the build folder when done building and copying files around.
The text was updated successfully, but these errors were encountered:
npm -v
): 6.14.15node -v
): 14.18.0node -p process.versions
):node -p process.platform
): darwinnode -p process.arch
): x64node -p "require('node-sass').info"
):npm ls node-sass
): 6.0.0The bug is a minor one, but when resolving
node-sass
through actions under Bazel, thebuild
folder that is created during the post install process has files with SHAs in them. That means that installs are not a cache hit because it changes between resolutions. The fix for this is just to have node-sass cleanup after itself on postinstall such that it removes thebuild
folder when done building and copying files around.The text was updated successfully, but these errors were encountered: