tsconfig paths not working when building for production

I’m submitting a…

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

When using Typescript paths in tsconfig, the project can be built with nodemon, but not with tsc (with npm run start:prod).

Expected behavior

I would expect the same code to work regardless its being built for development or production.

Minimal reproduction of the problem with instructions

1. Create a repo with Nest CLI
2. Add a path to tsconfig.json (for example @foo):

"paths": {
  "@foo/*": [
    "./*"
  ]
}

1. Change an import in app.module.ts: import { AppController } from '@foo/app.controller';
2. Run npm run start:prod

What is the motivation / use case for changing the behavior?

I had to remove every path alias in my code to get my project working for production. Since tsconfig paths are a default dependency of the project, and configured to work with nodemon, I believe it should also work when building for production.

Environment

Nest version: 5.1.0

 
For Tooling issues:
- Node version: 10.8.0  
- Platform: Windows