This has the downside that a third-party component would publish metadata with relative paths to angular2 that work only in their filesystem layout.

Discussed with @tbosch, both of us reached the conclusion that no resolution should occur across modules, and no symbol de-aliasing either.
Instead we should syntactically capture all the module's import statements, and leave references to other modules unresolved. The reader of the metadata is responsible for having a module resolver configured to resolve all of these.
Will work on another PR that does this.

going with #8256 instead

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.}