angular: Incorrect imports when targeting es2015 using ngc in Ng 4.x

I’m submitting a … (check one with “x”)

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

The particular issue I’m having is with ramda, but I believe it could apply to any other library that does not provide typings where we have to add the typings from @types.

Current behavior

When setting the target on tsconfig.app.json to es2015, the output code’s import statement for ramda library is incorrect:

import {uniq} from ‘ramda/index’;

Expected behavior

The import statement in the output file should be:

import {uniq} from ‘ramda’;

Minimal reproduction of the problem with instructions

I created a new app using the cli, and just changing the target on the tsconfig.app.json file to es2015. When you run npm run release, the build/app/app.component.js file contains the incorrect path to ramda.

Here is the repo to use to easily reproduce the issue: https://github.com/alvaro450/typings-issue

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

When creating a library, having the incorrect import statement would mean that when I use the library in an app, it will fail when it tries to resolve that import.

Please tell us about your environment:

MacOs Sierra, Visual Studio Code, npm 5

• Angular version: ^4.0.0

It is still an issue.

• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Browser independent, since this is the build process.

• Language: [all | TypeScript X.X | ES6/7 | ES5] Typescript

• Node (for AoT issues): node --version =
  6.10.0