Module path mapping is not working in generated js files

[lovedota]

TypeScript Version: 2.4.0

Code

• I have a config

"paths": {
      "pages/*": ["./app/pages/*", "../../pages/*"],
      "helpers/*": ["./app/helpers/*", "../../helpers/*"]
}

Expected behavior:

var element_helpers_1 = require("../../helpers/element-helpers");
var manage_documents_page_1 = require("../../pages/manage-documents-page");

Actual behavior:

var element_helpers_1 = require("helpers/element-helpers");
var manage_documents_page_1 = require("pages/manage-documents-page");

[kitsonk]

path does not change the emit... it simply allows TypeScript to resolve dependencies at design time that would otherwise not be automatically resolved. Whatever run-time module loader you are using would need to support any run-time configuration you need to reflect your desired run-time configuration.

[lovedota]

@kitsonk but actually I don't use webpack so that i cannot use alias for mapping, can we automatically generate the correct path from mapping table ?

[kitsonk]

Simple answer is no. TypeScript does not re-write module names. You will need to move the modules via external tooling or use a loader that allows mapping (e.g. like RequireJS or SystemJS).

[mhegazy]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.