Jürgen Wenzel

The original issue is fixed in alpha.39 and a PR is merged (https://github.com/aurelia/aurelia/pull/1534) for the new issue mentioned in the comment above. As soon as alpha.40 is out both of...

TL;DR: Change the link to `load="../another-sub-content@sub"`. Why: When using relative links in `load`, that is links that don't specify full path from root (not starting with `/`), the router looks...

@Vheissu The `instruction` parameter specifies the `RoutingInstruction` that resulted in the load _for the viewport_. It contains a `route` property that holds configured route data (if the load is the...

If you want the instruction responsible for the previously loaded component in a viewport, you can get it with ```ts load(_params, instruction) { console.log(instruction.previous); } ``` That doesn't feel convoluted...

The fix is in (https://github.com/aurelia/aurelia/pull/1501) and will be in the next release.

@aegenet Can you elaborate on this because I'm not seeing any issues in the gist you linked above.

@aegenet The test I had didn't cover your use case. I've created a new PR. Sorry for the trouble.

@christophano I've added a PR, https://github.com/aurelia/cli/pull/765, that will implement build targets. Do you think it will cover your needs? And if not, what's missing?

@christophano Target root can be outside of project root ("../sibling-folder-to-project/other-project-root") and target index and output are indeed relative to target root so that shouldn't be a problem at all.

I re-read your use case and just setting root: "../wwwroot" should do the trick (provided wwwroot is a sibling folder to Client).