Router swallows DI errors about aurelia HOT 7 CLOSED

I think any other DI resolving error (for example if some token cannot be injected because it is not registered in the container) would behave the same.

from aurelia.

What's wrong with my stackblitz? I tried to install the missing webpack-dev-server but it rejects it.

> webpack serve

[webpack-cli] You need to install 'webpack-dev-server' for running 'webpack serve'.
TypeError: callSite.getFileName is not a function. (In 'callSite.getFileName()', 'callSite.getFileName' is undefined)

~/projects/au2-conventions-pj6kbd 7s
❯ npm i -D webpack-dev-server
npm ERR! code ERR_INVALID_PROTOCOL
npm ERR! Protocol "https:" not supported. Expected "http:"

from aurelia.

Strange, for me the provided link works OK without any issues. webpack-dev-server is already listed in package-lock.json

from aurelia.

I managed to reproduce the error locally.
The endpoint is a resolver which right now our conventions plugin doesn't cover. Before we cover it, user needs to use explicit decorator on this resource. cc @Sayan751

from aurelia.

OK, I also saw that $isResolver: true fixes the issue. I don't know what's the design, use that meta flag, or there is a special decorator for resolver. cc @Sayan751

from aurelia.

$isResolver: true must be used for a valid resolver, a resolver interface requires it. I commented it out intentionally to show that an error thrown by DI system is caugth and swallowed by the router. It should not do it, so that developer may see what's the source of the problem.

from aurelia.

The doc asks you to write $isResolver: true. Why skip it?

https://docs.aurelia.io/getting-to-know-aurelia/overview/resolvers#example-of-a-custom-resolver

from aurelia.