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 current aurelia-types-installer npm package has CRLF EOLs in all the files. I'm guessing it was packaged on windows with git config core.autocrlf=true, which means that the bin/ati script as-packaged won't run on *NIX platforms because a carriage return ends up on the shebang line.
There is a fairly easy workaround, I just had to manually remove the carriage return from bin/ati after npm installed the package.
I suspect doing git config core.autocrlf input on windows might keep the newlines *NIX friendly for packaging on npm. (You can refresh an existing checkout by deleting .git/index followed by git reset... git status should then show what looks different without the autocrlf applied at checkout).
This isn't really a bug, but if you wanted to you could read this as an enhancement request to add a .gitattributes to maybe avoid this problem in the future.
Aluan,
The current aurelia-types-installer npm package has CRLF EOLs in all the files. I'm guessing it was packaged on windows with
git config core.autocrlf=true
, which means that thebin/ati
script as-packaged won't run on *NIX platforms because a carriage return ends up on the shebang line.There is a fairly easy workaround, I just had to manually remove the carriage return from bin/ati after npm installed the package.
I suspect doing
git config core.autocrlf input
on windows might keep the newlines *NIX friendly for packaging on npm. (You can refresh an existing checkout by deleting .git/index followed by git reset... git status should then show what looks different without the autocrlf applied at checkout).This isn't really a bug, but if you wanted to you could read this as an enhancement request to add a .gitattributes to maybe avoid this problem in the future.
Some similar discussion can be found at npm issue 2097.
Have a nice day!
The text was updated successfully, but these errors were encountered: