feat(dev): better DI error messages for instantiation

[bigopon]

📖 Description

Currently, when there is an error during the instantiation of a class, there is not enough information what went wrong. This is quite an issue once there are multiple changes being added in at once, like in a dependency upgrade.

Enhance the DEV mode error message by catching the dependency resolution error while instantiate, so that there will be more information for debugging.

Examples

1. for the following code with inject:

   export class App {
     static inject = [class Abc {
       constructor() {
         throw new Error('testing testing');
       }
     }]
   }

   The error messages logged will look like this:

   

2. For the following code with resolve:

   export class App {
     abc = resolve(class Abc {
       constructor() {
         throw new Error('testing testing');
       }
     });
   }

   The error messages logged will look like this
   

🎫 Issues

Resolves #913

cc @xenoterracide @Sayan751 @fkleuver

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.52%. Comparing base (32f00ed) to head (0120642).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1917      +/-   ##
==========================================
+ Coverage   88.47%   88.52%   +0.04%     
==========================================
  Files         260      260              
  Lines       22843    22843              
  Branches     5258     5258              
==========================================
+ Hits        20211    20222      +11     
+ Misses       2632     2621      -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Sayan751]

Thanks @bigopon for this nice change! I think most of the devs won't use the dev/builds by default. Hence, I think we should have the same information also for non-dev builds.

[bigopon]

@Sayan751 if a serious app was to be public, it needs to be first developed in dev mode before a prod build, and thus, error like this will be prominent and get ridden of, so this scenario we don't need these errors in prod mode.
If an app was a non serious one, it can just use dev build for both development and production, and will still be fine.
I think we shouldn't carry this experience enhancement into our prod build.

[Sayan751]

In that case, I think we should have "recipe" documentation on how to enable the dev mode. As it might not always be straightforward.

[bigopon]

@Sayan751 thanks, and agree, Ive been thinking of an faq doc or something to describe these.

[tareqimbasher]

@bigopon @Sayan751 This is a great addition but can't find any documentation on how to use dev mode. Can you provide some info on how I would go about that? Thank you!

[Sayan751]

@tareqimbasher Here is an example how to use development builds: https://github.com/aurelia/new/blob/master/webpack/webpack.config.js#L120

[tareqimbasher]

@Sayan751 Great, thank you! Plugged in those aliases and its working.