feat: control which linefeed character to use #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Allow the user to control which linefeed character to use.
Why:
Babel does not care about line endings and always uses
\n
, which means you're forced to keep the output files in the same format for fixtures to work. Which in a repository wherecore.autocrlf = true
means extra config files and mixing the linefeed used in the repository. This is an unnecessary process that can be eliminated.How:
After babel has transformed the code run a regex to replace the line endings with either
\n
,\r\n
, the system default, or preserve from input, depending on what the user specifies.