-
Notifications
You must be signed in to change notification settings - Fork 13k
Description
I am experiencing problems when trying to build a TypeScript project which resides on one of our network shares. I am using Windows 7.
The problem only occurs when using node module resolution and seems to be related to the mapping of network drives to UNC paths.
Suppose I have the following setup:
A drive X: mapped to \\server\projects with a folder test containing my files.
TypeScript Version: 2.0.6
Code
// module.ts
export interface A {}
// index.ts
import { A } from './Module'
// tsconfig.json
{
"compilerOptions": {
"target": "es2015",
"module": "commonjs"
}
}
Expected behavior:
No errors.
Actual behavior:
======== Resolving module './module' from 'X:/test/index.ts'. ========
Module resolution kind is not specified, using 'NodeJs'.
Loading module as file / folder, candidate module location 'X:/test/module'.
File 'X:/test/module.ts' exist - use it as a name resolution result.
Resolving real path for 'X:/test/module.ts', result 'UNC/server/projects/test/module.ts'
======== Module name './module' was successfully resolved to 'UNC/server/projects/test/module.ts''. ========
index.ts (1,24): error TS2307: Cannot find module './Module'.