fix(build): use baseUrl and paths from tsconfig

[filipesilva]

Supersedes #2210 #2392 #2428.

Uses same base mechanism as @abner's #2210, but edits the new webpack-build-typescript.ts and adds tests.

Does NOT currently work for --aot (/cc @hansl).

[hansl]

Awesome!

[glipecki]

That's awesome ;) Thanks!

[abner]

Awesome!!!!

[arlowhite]

@filipesilva What issue can I follow that tracks support for --aot with @app tsconfig paths?

I use @app paths and ng build -prod is broken.

[altschuler]

@filipesilva Would you have any pointers as to what could be done as a workaround for aot support? Thanks!

[filipesilva]

@arlowhite @altschuler I'm not sure what the problem you are describing is, AFAIK TS paths work for aot. Can you open a new issue with a repro of what you're experiencing?

[arlowhite]

@filipesilva I'm not sure custom paths are the root cause. You can ignore my comment.

Just FYI...

My AOT build with -prod broke a while back ~1.0.0. At the time, the error message made me think it was related to my @app path in tsconfig.json. But I think it is unrelated. The -prod aot build seems to have become much more strict since 1.0.0

I started to work on fixing the -prod build and made some progress. One issue was

  animations: [
    trigger('fade', [
      state('hide' as FadeState, style({

The as FadeState cast doesn't work with AOT. The error was cryptic and I thought it was an issue with importing my FadeState type. Removing the cast fixes the import error I was seeing.

After fixing that, I got hundreds of errors reporting that Component fields were private that needed to be public for AOT. I haven't had time to work through those issues yet, so don't know if the build will actually work now.

[altschuler]

@filipesilva Please ignore, problem turned out to be something completely different, baseUrl and paths work great with aot :)

[filipesilva]

@arlowhite there was a bug pre-1.0 that was hiding a lot of AOT errors (like the private members), and was discussed #5623. This did result in a lot more AOT errors being reported in 1.0. They were mostly 'real' AOT errors though, and a few that weren't were fixed.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}