| 9 Jan 2024 |
 samasaur | the shebang is /usr/bin/env bash and there is no /usr/bin/env | 01:46:31 |
 @julia:the-apothecary.club | probably want to add the patchshebangs hook to your package build then | 01:47:06 |
| samasaur | is that a thing I can do? | 01:47:22 |
| samasaur | I was just going to change the little script to point to the bash package | 01:47:31 |
| @julia:the-apothecary.club | yeah that'll automatically rewrite the shebangs to point to nix store paths | 01:47:35 |
| @julia:the-apothecary.club | * yeah that'll automatically rewrite the shebangs to point to nix store paths, which means your script can work on-not-nix as well | 01:47:51 |
| samasaur | won't it work anyway if I point it to the nix bash | 01:48:24 |
| samasaur | * won't it work anyway if I point it to the nix bash? | 01:48:25 |
| @julia:the-apothecary.club | it'd work, just not if you don't have nix? which you may or may not care about | 01:49:04 |
| samasaur | it should work, i think. because either you are building the package from the nix definition, in which case you have nix, or you are using this docker image, which will have that nix bash in it | 01:49:53 |
| @julia:the-apothecary.club | ok | 01:50:14 |
| samasaur | i guess it wouldn't work if you built it using npm normally but if you do that then you wouldn't have the script at all | 01:50:15 |
| samasaur | okay well it did NOT work | 01:53:49 |
| samasaur | however | 01:53:51 |
| samasaur | * okay well it did NOT work, i got the same error | 01:54:20 |
| samasaur | when i entered a shell in that new container and ran the script via bash directly, i got a different error | 01:54:22 |
