Jens Reimann

@NiklasEi can you post the console output of that panic? @OmmyZhang can you take a look?

I took a brief look into this. And I am not sure this is achievable. I personally would also like to to just run: ``` trunk serve --example foo ```...

Maybe … however, so far (due to the way cargo works) we always ended up having the UI excluded from the main workspace. Still keeping things in the same repository....

No that I am aware of. But yes, that would be a nice addition.

> We implement a similar approach to what is described in https://github.com/trunk-rs/trunk/issues/9 I think that describes a bunch of ideas :) … What exactly do you propose?

so that would be part of the frontend code and compile when trunk would call `cargo build`, right? I assume that will create a tree of assets at some location,...

I think it would be worth exploring this idea. I also think there could be multiple levels of integration. Maybe it makes sense forking off an issue working towards this....

Created a new issue: https://github.com/trunk-rs/trunk/issues/759

Thanks for the PR. I did a quick look at it, and rebased it too. I think it needs some more work, but goes in the right direction. What I...

The whole idea of using `./` as a default seems to work quite poorly when using the browser's History API. A reload of the page with a sub-path then turns...