feat: support webserver for speedscope cli

[damienwebdev]

I'm working with callgrind files in a devcontainer. Unfortunately, this means that the "open in browser" behavior native to speedscope doesn't quite work "out of the box".

If possible, I'd love to see a little webserver built into speedscope so that I can run something like:

speedscope cachegrind.out.38776.gz --serve
Serving speedscope on http://localhost:46387

so that I can just quickly visualize the callgrind file.

Optionally, and I don't know how big an ask this is, it would be nice to extract all the various Parser -> ProfileGroup behaviors out of the react app into a separate lib so that I could potentially write this little server myself. In its current state, speedscope encapsulates the entire react app onto npm making it difficult to extend.

Aside, this project is awesome.

[jlfwong]

Hi @damienwebdev!

Re: including a small buit-in web server, I'll think about it. That's a pretty reasonable suggestion, and I can see scenarios where that would be useful!

Regarding this:

Optionally, and I don't know how big an ask this is, it would be nice to extract all the various Parser -> ProfileGroup behaviors out of the react app into a separate lib so that I could potentially write this little server myself. In its current state, speescope encapsulates the entire react app onto npm making it difficult to extend.

You're definitely welcome to fork the project and make this library! An agent would honestly do a pretty good job with this.

I'm not interested in doing that as part of this project because I don't want to maintain a stable library API. Speedscope is intentionally designed as an open source application, rather than an open source library, so that I can change internals however I'd like

[damienwebdev]

@jlfwong Ok. I've taken a stab at adding the --serve flag myself.