LF / CRLF line ending issues when building
See original GitHub issueHey there,
node-minify
is awesome and I use it a lot of my projects. Recently I bought a Windows machine and now do cross-platform web development from it and my MacBook. It seems that when I build with node-minify
on Mac it keeps LF
line endings, but on Windows throws CRLF
line endings. This is problematic because Git seems to think there are a number of new changes when there aren’t. This even happens when I have git config --global auto.crlf true
…
Has anyone else run into this issue?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Git replacing LF with CRLF - windows - Stack Overflow
-crlf This tells Git to ignore the line endings for all files. And does not change the files in your working directory. Even...
Read more >CRLF vs. LF: Normalizing Line Endings in Git
Line endings can differ from one OS to another. Learn the history behind CRLF and LF line endings and how to enforce line...
Read more >issue with CRLF line endings - Google Groups
warning: CRLF will be replaced by LF in src/sage/misc/element_with_label.py. The file will have its original line endings in your working directory.
Read more >How to Get Consistent Line Breaks in vs Code (LF vs CRLF)
At the bottom right of the screen in VS Code, click the little button that says LF or CRLF . After changing it...
Read more >Fixing misaligned Linux and Windows line endings
The reasons don't matter: Windows chose the CR/LF model, while Linux uses the \n model. So, when you create a file on one...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey there. So after additional poking it was actually because files I was feeding into the
compressor
were actually read and written by node’s file system prior to being sent to you. As a result the issue wasn’t with node-minify at all. Thanks for such a great module!Thanks for the support! I’ll let you know if I come to any other conclusions as well.