Patrick Hulce

A question for @makslevental and others who've hearted, are you primarily interested in *incoming* network requests i.e. inspecting server routes, or *outgoing* network requests made by node?

Yeah makes sense I've just been thinking lately that it'll require a completely new UX. I'd love to see incoming routes with a breakdown of time spent in each middleware,...

For additional info, it seems like this might be an artifact of too smart commonjs compat which uses the `Link` defined on `Router` instead of the `export {..., Link}`. I'm...

I was indeed importing from root according to the previous docs. Why is `import { Link } from 'preact-router'` not the link with matching behavior?

Awesome work @vladmandic thank you for sharing! Can I buy you a beer/do you have a tip jar anywhere? :D (and @justadudewhohacks too if you're still around 😃 )

I think what you're looking for here is something similar to the "manifest" output requested in `target=filesystem` feature. https://github.com/GoogleChrome/lighthouse-ci/issues/142#issuecomment-579830878 the output would look something like this then? ```js output: {...

Thanks for filing @schlessera! I like this feature request as a generic run comparison view where any URL from any build could be compared with any other.

There is no timeline for anyone working on this in the near future. It's open source though so feel free open a PR ;)

There's [architecture documentation](https://github.com/GoogleChrome/lighthouse-ci/blob/master/docs/architecture.md) that's definitely a must, but nothing really specific to the server UI implementation. I'll add some notes on it to CONTRIBUTING.md 👍

FYI some guidance is now in @gauthampughaz #359