Lower case drive letter in Open New Command Prompt command on Windows

[rob3c]

BUG REPRO HERE: https://github.com/rob3c/tsc-tsnode-vscode-casing-bug-on-windows

Overview

Starting with the 2016-07-14 release of Visual Studio Code Insiders edition (and now released in regular VS Code 1.3.1), the behavior of the Open New Command Prompt command (ctrl+shift+C) changed on Windows. Now, it lower-cases the drive letter in the new console's prompt, and that seems to affect the ability of at least ts-node (and possibly other tools) to build typescript code when the forceConsistentCasingInFileNames compiler option is set in tsconfig.json.

Step 1 - Open two command prompts for comparison

• Within VS Code, invoke the Open New Command Prompt command via ctrl+shift+C (or find it using View | Command Palette... in the menu). Notice that the drive letter in the prompt is lower case now!
• Open a standard Windows Command Prompt outside of VS Code in the normal way, and navigate to this project's root folder. Notice that the standard console has a captial drive letter.

Step 2 - create some source files

// tsconfig.json
{
    "compilerOptions": {
        "forceConsistentCasingInFileNames": true,
        "module": "commonjs",
        "moduleResolution": "node",
        "outDir": "bin",
        "target": "es5"
    },
    "exclude": [
        "bin",
        "node_modules"
    ]
}

// foo.ts
export class Foo {
    constructor(public bar: string) {}
}

// index.ts
import { Foo } from './foo';
let foo = new Foo('bar');
console.log(JSON.stringify(foo));

Step 3 - Build successfully using typescript directly

> tsc

This builds successfully in both command prompt windows.

Step 4 - Break stuff!

> ts-node index.ts

This builds and runs successfully in the standard Windows command prompt that has an upper-case drive letter, but it breaks in the console window that VS Code opens with this error:

C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\index.ts:280
        throw new TSError(diagnosticList)
              ^
TSError: ? Unable to compile TypeScript
index.ts (1,21): File name 'C:/dev/bug-repros/tsc-tsnode-vscode-casing-bug-on-windows/foo.ts' differs from already included file name 'c:/dev/bug-repros/tsc-tsnode-vscode-casing-bug-on-windows/foo.ts' only in casing (1149)
    at getOutput (C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\index.ts:280:15)
    at compile (C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\index.ts:289:14)
    at loader (C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\index.ts:304:23)
    at Object.require.extensions.(anonymous function) [as .ts] (C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\index.ts:321:14)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Function.Module.runMain (module.js:575:10)
    at Object.<anonymous> (C:\dev\bug-repros\tsc-tsnode-vscode-casing-bug-on-windows\node_modules\ts-node\src\_bin.ts:172:12)
    at Module._compile (module.js:541:32)

BUG REPRO HERE: https://github.com/rob3c/tsc-tsnode-vscode-casing-bug-on-windows

[kieferrm]

More details:
This only happens when the window has an open folder, i.e. you opened a real workspace. When there is no open folder the drive letter is still upper case.

Assigning to @Tyriar since he was the most active in the terminal area recently.

[rob3c]

@kieferrm thanks, I just confirmed that opening Code without any file or folder will keep the drive upper-case. However, I still see the drive lower-cased if I right-click on a single file in Explorer and choose Open with Code so that just the file is opened and the explorer panel says "you have not yet opened a folder". Maybe this helps narrow it down a little more?

[alexperovich]

I am hitting this exact same issue using gulp-typescript to compile typescript files through a build task. Turning off the compiler option is a workaround but that can cause issues on non-windows.

[hh10k]

VSCode using c:\ instead of the usual C:\ is annoying because it breaks all the code that makes incorrect assumptions about paths.

I think the real bug is this: microsoft/TypeScript#10095