Use pre-existing line endings in `tsconfig.json`

[msssk]

Commit 075ebfa introduced the behavior of using the OS default for line endings in tsconfig.json. This is undesirable behavior for people who use a line ending different from the OS default. Until Atom supports configurable line endings, atom-typescript should read the line endings from the existing tsconfig.json file and use those.

[yoav-zibin]

Any updates on this?
I need to be able to use both atom-typescript and tsc (the regular compiler),
and I can't get them to produce the same results because of the line ending difference :)
I wish to have just newlines:
"newLineCharacter": "\n",
but if I look at the output I see atom-typescript adds "^M" :
var langCodeToName = {};^M

[yoav-zibin]

I think newLineCharacter was the old way of setting it in the formatCodeOptions

"formatCodeOptions": {
    "newLineCharacter": "\r\n", 

I tried newLine compiler option:
"compilerOptions": {
"newLine": "CRLF"

http://json.schemastore.org/tsconfig
"newLine": {
"description": "Specifies the end of line sequence to be used when emitting files: 'CRLF' (dos) or 'LF' (unix).",
"enum": [ "CRLF", "LF" ]
},

https://github.com/Microsoft/TypeScript/wiki/Compiler-Options
--newLine Use the specified end of line sequence to be used when emitting files: 'CRLF' (dos) or 'LF' (unix)."

But it doesn't work for me even with "tsc" so I opened:
microsoft/TypeScript#5968

Nothing I do can make tsc and atom-typescript produce the same line endings...
Any ideas?

[yoav-zibin]

Ok, solved it by upgrading my tsc compiler to latest version, and now newLine: CRLF works,
and the two compilers produce the same output (they still have some minor discrepancies, but nothing some typecasts can't fix).
Still would be nice to support newLine in atom-typescript :)