It seems like overkill to slow down every single build for the sake of not having to run npm run clean or whatever, once, when you change file casing in the extremely rare case where it actually matters.

At the end of the day I only see two output : will I be able to use TypeScript without pain or not ? The answer is yes only on a non-Microsoft system. For a software developed by Microsoft. Do you get it ?

Also, people want you to handle this issue. Just handle it. Why wouldn’t you ? Windows is not gonna become case sensitive tomorrow, and we will

never

run a clean before each compilation. So you are the only one who can fix this.

I’m sending this to twitter, because you really behave like kids. You should be ashamed of yourself.

You don’t have to rename the file, just always do this:

var file = ...;
fs.unlink(file, function() {
  fs.writeFile(file, ...);
});

Doing an unlink should be fast, and then the output case will be what is expected.

The compiler does not do any thing special here. this is the node fs apis on windows

c:\test>node
> const fs = require("fs");
undefined
> console.log("Foo.js first");
Foo.js first
undefined
> fs.writeFileSync("./Foo.js", "a");
undefined
> fs.writeFileSync("./foo.js", "a");
undefined
> console.log(JSON.stringify(fs.readdirSync("./"), undefined, 2));
[
  "Foo.js"
]
undefined
>
> fs.unlinkSync("./Foo.js");
undefined
>
> console.log("foo.js first");
foo.js first
undefined
> fs.writeFileSync("./foo.js", "a");
undefined
> fs.writeFileSync("./Foo.js", "a");
undefined
> console.log(JSON.stringify(fs.readdirSync("./"), undefined, 2));
[
  "foo.js"
]
undefined
>