Path mapping module resolution - #5728

I suppose this can solve problems I had using angular2 with jspm with Visual Studio. How can try if this works?

Great, I'll try this out as soon as it is merged :)

can you add test with suffix in paths matching like

"paths": {
     "generated/*/folder1" : ["build/folder1"]

as well as the case when there are multiple match but we pick the longest one (so we have a record of what we use to do in case of future change)

Also what happens in this case:

    "rootDirs": [
        "*",
        "generated/*" 
    ],

is this allowed? if so could we have some tests as well? (from the spec, it seems so. I can't tell from the comment though)
also what happen:

    "rootDirs": [
        "*",
        "generated/*/folder1" 
    ],

Yui (@yuit)

• sure, I can add test for path mappings where '*' appear in the middle of the substitution string
• "' * ' in rootDirs" this is part that slightly diverges from the spec (I have not updated it yet): since rootDirs are always prefixes, the only shape where '*' makes sense is <prefix> *. To avoid confusion now rootDirs are just strings.

Can you enable the --traceModuleResolution option when running through the language services?

Sure, I'll add it in the next iteration of this PR

Here is my folder structure

├───app
│       app.ts
│       tsconfig.json
│       webpack.config.js
│
└───libs
    └───guid
        │   package.json
        │
        ├───dist
        │       guid.d.ts
        │       guid.js
        │       guid.js.map
        │
        └───src
                guid.ts
                tsconfig.json

libs/guid/package.json:

{
  "name": "guid",
  "version": "1.0.0",
  "main": "dist/guid.js",
  "typings": "dist/guid.d.ts"
}

app/app.ts:

import guid from 'libs/guid';

console.log(guid());

app/tsconfig.json

{
    "compilerOptions": {
        "declaration": true,
        "module": "commonjs",
        "noImplicitAny": true,
        "removeComments": false,
        "sourceMap": true,
        "outDir": "dist/",
        "target": "es5",
        "moduleResolution": "baseUrl",
        "baseUrl": "",
        "paths": {
            "libs/guid": ["../libs/guid/dist/guid.d.ts"]
        }
    },
    "exclude": [
        "dist"
    ]
}

Rather than specifying paths as "libs/guid": ["../libs/guid/dist/guid.d.ts"] would it be possible to only specify "libs/guid": ["../libs/guid"] and if package.json with typings exists refer to it? This way the libs/guid/package.json controls the entry point rather than caller.

Also how do I set path mappings in csproj?

I'm currently making a few adjustments to this PR based on results of the latest design meeting and I think that your initial scenario should be supported. Regarding specifying path mappings in .csproj - this won't work, paths and rootDirs will be options that can be specified only via tsconfig.json

Vladimir Matveev (@vladima) Would really love to see it working in csproj since that is what we are using internally.
Or is there any way to tell csproj to use tsconfig.json?

I was expecting something like this in csproj.

<TypeScriptPath>
  <Pattern>libs/guid<Pattern>
  <Substitution>../libs/guid</Substitution>
<TypeScriptPath>

👍

which version of typescript and gulp-typescript support this?

which version of typescript

TypeScript@next and should be in the next release TS 2.0