Typescript ignores typings when using tsconfig.json paths

[WoMayr]

TypeScript Version: 2.3.4, 2.4.2, 2.5.0-dev.20170801

fabric@1.7.17 and @types/fabric are installed.

Code

tsconfig.json

{
    "compilerOptions": {
        "target": "es5",
        "module": "commonjs",
        "baseUrl": "src/",
        "sourceMap": true,
        "outDir": "dist/out-tsc",
        "paths": {
            "fabric": [ "../node_modules/fabric/dist/fabric.require.js" ]
        }
    },
    "exclude": [
        "node_modules"
    ],
    "compileOnSave": false
}

src/app.ts

import * as fabric from "fabric";

window.addEventListener("load", function () {
    const canvas = new fabric.Canvas("my-canvas");

    // create a rectangle object
    var rect = new fabric.Rect({
        left: 100,
        top: 100,
        fill: "red",
        width: 20,
        height: 20,
        lockUniScaling: true
    });

    // "add" rectangle onto canvas
    canvas.add(rect);

    // canvas.toSVG() is faulty inside definitions
    console.log(canvas.toSVG());
});

Expected behavior:
TSC should report an error that toSVG needs parameters.

Actual behavior:
typescript doesn't load any type definitions for the fabric module.

[DanielRosenwasser]

If you have .d.ts files available, why are you re-mapping to the .js file which has no type information associated with it? That's why it's not working the way you expect.

In fact, why are you even using paths if you have the @types package available? When targeting commonjs (or using nodejs for your moduleResolution strategy) the .d.ts files should automatically get picked up.

[WoMayr]

I do understand. The problem is, that I am using it in the context of an angular4 project using angular-cli. Angular-CLI does not support aliasing or at least only using the information from paths (See angular/angular-cli#6282).

But to use fabric.js with import I need to use a different file than the one stated in the package.jsons main field or the typings from @types/fabric won't fit. My hope was that with paths I can target the correct JavaScript file and I expected it to leave the connection to the typings intact as it was even suggested from the angular-cli team.

I somehow thought that it might be a bug with tsc but thinking at it again: paths only tells tsc where to look for the typings at it does not alter the imports itself. So no wonder it doesn't work as I expected it.

Is there a way to use paths and still have the type information available or at least attach it manually? I tried adding ../node_modules/@types/fabric to the fabric entry in paths but that didn't work (desperate attempt).

[mhegazy]

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