- Notifications
You must be signed in to change notification settings - Fork21
fix #9 by using LF line-endings#10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
this ensures that the bin scripts in the published package are unix-compatible
Thank you for this contribution 🙇 |
whyboris commentedJan 4, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Thank you again for this -- I'll test it onWindows once and merge 🤝 This was a great article about the topic: I might try the command from the article |
Intending to merge/fix this problem in the coming month 🤞 |
I'm hoping to catch up on updating all my repositories this winter 😅 |
😓 oh it's been busy years for me ... hoping to get back to cleaning my less-frequently-used-by-me repositories in 2025 🤞 Thank you again for the PR - it's not forgotten 🙇♂️ ♥ |
Uh oh!
There was an error while loading.Please reload this page.
fixes#9
After merging this in, to actually see the fixed line-endings in your working tree, you'll need to clear out your working directory, and then restore everything again by doing this:
(N.B. this will clear out any uncommitted changes you have on your branch).
Then if you open
bin/index.js
you should see that the line-endings are just LF rather than CR+LF. I tested this in Notepad++ (View > Show Symbol > Show End of Line).