Hi, thanks for trying it out! The server crashed, sorry about that. I need to add a liveness check. It should be working now.
As for comments asking to install React, it's a bug on my end. Create-react-app leaves a manifest.json file in public/, which causes the prompt to appear. I've deleted it in the latest container image but haven't redeployed yet since we've got a lot of active users at the moment.
Anyway, you don't have to install anything, nor will you ever have to, in order to use Asqi.
3main.5cc1145c.js:2 TypeError: Cannot read properties of undefined (reading 'p')
at V.rpc (main.5cc1145c.js:2:23177)
at V.server_repos (main.5cc1145c.js:2:25611)
at e (main.5cc1145c.js:2:93041)
Looks like it's working now - I tried out the gitlab repo. My laptops fans spun up, mousing over segments seem to freeze the UI, and I wasn't really sure what I was looking at in the first place. I think the app itself is pretty disorienting, especially compared with the simplicity of the landing page. Have you considered pre-rendering all this stuff and making the app more static? I think a significant improvement could be to change whatever is happening on hover to on click, otherwise UI elements are shifting around a lot and stalling as it synchronously retrieves elements. I really like the idea of an OSS codebase explorer though, hope you keep iterating on this project!
Yeah the locking up is a big issue right now. It happens when you first load a repo and the client populates its local IndexedDB with all the RPC data coming down, which is 10-100k insertions and causes browser slowness. I've tried a couple of strategies that run them in timed batches to avoid overwhelming the browser, but it still has trouble especially on big repos. If you know of a way to bulk-load IDB without browser issues, let me know; my next strategy is probably just going to be either to defensively trickle-load or maybe try to measure microtask wakeup times to detect event loop load for backoff. Once I get it right I'll write a blog post about it because it's an unexpectedly challenging problem.
The good news, though, is that the load delays happen only the first time: if you let it warm up once and reload later, it should be much snappier because IDB reads are much faster than IDB writes.
The hover on click idea came up in another reply and I really like it as an option you can choose. That's going to be a high priority for the next release, I'm glad you also mentioned it.
Pre-rendering is a very good idea and while I had considered it before, your comment has me thinking about a much more general use case for it. I think it might enable some very snappy UI behavior, particularly around time-scrubbing or timelapse animations. I'm really glad you said something; this might lead to something very cool.
Thanks for the kind words and thoughtful feedback!
Yeah you definitely don't need to install anything. I don't know how to deploy React apps apparently (will try to fix), but it's just a regular website and I would never ask users to expect anything else.
Update: it's because create-react-app creates manifest.json in public/, which causes Chrome to prompt you for this. I've deleted it in the latest container image and I'll redeploy once traffic dies down a bit.
Nope still there, but you may have caught the server at a bad moment. Because Asqi uses the DB read/write, there's only one replica of the server and it has less than 100% uptime depending on indexing and user load.
As for comments asking to install React, it's a bug on my end. Create-react-app leaves a manifest.json file in public/, which causes the prompt to appear. I've deleted it in the latest container image but haven't redeployed yet since we've got a lot of active users at the moment.
Anyway, you don't have to install anything, nor will you ever have to, in order to use Asqi.