Description
TypeScript Version: 2.0.2
Code
tsconfig.json
{
"compilerOptions": {
"target": "ES6",
"module": "commonjs",
"baseUrl": ".",
"paths": {
"foo/*": ["*"]
}
}
}app.ts
import {Foo} from 'foo/utils';
console.log(Foo);utils.ts
export const Foo = 'Foo';Expected behavior:
% ./node_modules/.bin/tsc && node app.js
FooActual behavior:
% ./node_modules/.bin/tsc && node app.js
module.js:457
throw err;
^
Error: Cannot find module 'foo/utils'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/home/mfischer/src/videmo/tsc-test/app.js:2:17)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)app.js
"use strict";
const utils_1 = require('foo/utils');
console.log(utils_1.Foo);Typescript i
5EFA
s finding the right module, but in the emitted code, the module path is left as-is instead of applying the path aliases from tsconfig.json. Obviously node has no idea where to find the module. I would have expected typescript to resolve the module path and replace it with something that node can resolve.
If this behavior is intended, then how can the path maps be used to solve the relative-import-hell in conjunction with node?