Improve error message for when Injectable() is missing #12467

I'm submitting a ...

[x] bug report

Current behavior
If component A has a dependency on service B, but service B does not have the Injectable() decorator defined, a vague error message is thrown:

Can't resolve all parameters for SomeService: (?, ?)

This is the exact same error message for when dependencies can't be loaded. Up until now that error message was given because I use barrel files and the order of import/exports should be adjusted. Thus, I was thrown off when trying to fix this problem.

Expected behavior
A specific error message like:

SomeService was provided, but an `Injectable()` decorator was not found

Minimal reproduction of the problem with instructions

• Create a service, but omit the Injectable() decorator. This service should have a dependency to at least one other service (defined correctly).

  import { Injectable } from '@angular/core';
  
  // oops, forgot the decorator
  export class SomeService {
    constructor(private otherService: OtherService) { }
  }
  
  @Injectable()
  export class OtherService { }
  

• Provide the services with the module.

• Create a component that gets the SomeService injected.

I used the Plnkr of the Angular quickstart to reproduce this problem. On the Car service in app/car/car.ts, I simply removed the decorator. The console immediately shows the error:

Can't resolve all parameters for Car: (?, ?)

// Edit:
In the documentation, it is mentioned that the injector will throw a NoAnnotationError, but the link to NoAnnotationError results in a 404.

What is the motivation / use case for changing the behavior?
A more precise error message would direct me to the problem instantly and the problem could have been fixed in a matter of seconds. Because this message is the exact same as when dependencies can't be resolved due to import/export order with barrel files, it now took me 30 minutes of stripping dependencies and order checking before I noticed this simple and tiny mistake.

Please tell us about your environment:
Windows 10, Chrome 53 and SystemJS as the module loader.

• Angular version: 2.0.0 and upwards. It is still a problem in 2.1.0.
• Browser: The web application crashes in all browsers. Chrome 53 and Edge 38 clearly show the error in the console. Firefox however, shows a CompileMetadataResolver and I'm not able to find a more specific error message.
• Language: TypeScript 2.0.3.
• Node (for AoT issues): 6.0.0.