In the "Working with line-ends special symbols LF/CRLF" section of the documentation we can see:

The special template variable _new_lines enforces a specific line ending. Acceptable variables: '\n\r' for CRLF and '\n' for POSIX.

Here is example how to force line endings to CRLF on any deployment:

{
    "project_slug": "sample",
    "_new_lines": "\n\r"
}

But this order is mistaken, since:

"The traditional order, when both control characters are used, is Carriage Return, then Line Feed.

The reason for this goes back to the old ASR-33 Teletype.

When a Carriage Return is issued to an ASR-33, the print head, if it is near the right margin, takes over a tenth of a second to return to the left margin, plus there is a bit of "bounce" when the left margin is hit.

If the order were Line Feed, then Carriage Return, the first printed character might occur a tenth of a second after the Carriage Return, and thus might end up printing (as a smear) halfway across the page. But if Line Feed comes after Carriage Return then the time taken by the Line Feed provides extra time for the print head to complete it's trip."

StackOverflow

So this PR aims at fixing the CRLF order to the traditional '\r\n'