Can't install sass/dart-sass

[Birdie0]

bin fails to install sass binary.

> bin install --debug github.com/sass/dart-sass
   • debug logs enabled
   • Config directory is: /home/user/.config/bin
   • Download path set to /home/user/.bin
   • Getting latest release for sass/dart-sass
   • Removing dart-sass-1.52.3-windows-x64.zip (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941112) with score 11 lower than 21
   • Removing dart-sass-1.52.3-windows-ia32.zip (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941109) with score 1 lower than 21
   • Removing dart-sass-1.52.3-macos-x64.tar.gz (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941245) with score 11 lower than 21
   • Removing dart-sass-1.52.3-macos-arm64.tar.gz (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941261) with score 6 lower than 21
   • Keeping dart-sass-1.52.3-linux-x64.tar.gz (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941024) with highest score 21
   • Removing dart-sass-1.52.3-linux-ia32.tar.gz (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941004) with score 11 lower than 21
   • Removing dart-sass-1.52.3-linux-arm64.tar.gz (URL https://api.github.com/repos/sass/dart-sass/releases/assets/67941531) with score 16 lower than 21
   • Checking binary from https://api.github.com/repos/sass/dart-sass/releases/assets/67941024
   • Starting download of https://api.github.com/repos/sass/dart-sass/releases/assets/67941024
3.39 MiB / 3.39 MiB [-------------------------------------------------------------------------] 100.00% 30.51 MiB p/s 1s
   ⨯ command failed            error=Error installing binary: open /home/user/.bin: file exists

[marcosnils]

yep, seems like a bug. You can bypass it by specifying the binary path in the download with:

bin install github.com/sass/dart-sass ~/.bin/sass

Cheers!

[marcosnils]

Wait.. something's not right... bin doesn't seem to be properly uncompressing the binary. Let me check real quick

[marcosnils]

Seems like something that the underlying file detection library is not being able to parse. Just referenced the issue here.