Custom paths not working

[Christoffer Skogh]

When setting custom paths they don't seem to work, I think it's because of AOT but I'm not sure. It breaks both when I build the project and when I test it. I use the same paths in my CLI project and it works fine so I guess there's some config missing in this project but I haven't been able to figure out what.

I use this tsconfig:

{
  "compilerOptions": {
    "baseUrl": ".",
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "noEmit": true,
    "sourceMap": true,
    "declaration": false,
    "noImplicitAny": false,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "lib": [
      "es2015",
      "dom"
    ],
    "typeRoots" : [
      "./node_modules/@types"
    ],
    "types": [
      "jasmine",
      "karma",
      "node",
      "webpack",
      "webpack-env"
    ],
    "paths": {
      "@shared/*": ["src/*"],
      "@components/*": ["src/components/*"],
      "@directives/*": ["src/directives/*"],
      "@modules/*": ["src/modules/*"],
      "@pipes/*": ["src/pipes/*"],
      "@validators/*": ["src/validators/*"]
    }
  },
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "src/**/*.spec.ts",
    "node_modules",
    "demo",
    "dist"
  ]
}

[Vladimir Tolstikov]

@chrillewoodz I'm not using custom paths there and all's fine. Why do you need them?