Cool... haven't looked at the code, but thought it would be nice to do a CSV parser as a stream though... either sync or async... able to do for-of loops on the input itself... an inner parser yielding each column, then yielding the row as a set.
Either way, nice to see the progress on this.
The conversion seems to assume that the API in question supports callback or promise results... While many newer libraries will, plenty will be either or.
Deleted the duplicate posts... leaving this. Note: this is a JS content related site... see the about page[1]. While your tool looks interesting, it's really headed into off topic territory.
FTR, I've been playing with Rust, tauri and yew... the whole space is very cool along with support for wasm tooling. It's just off topic in this space. You may want to post to Hacker News[1] or other more general developer groups. Alternatively, if you wrote an article showing how you can integrate this with say package.json for a node project, or with Deno... that would at least be borderline.
1. https://www.echojs.com/about
2. https://news.ycombinator.com/
Deleted the duplicate posts... leaving this. Note: this is a JS content related site... see the about page[1]. While your tool looks interesting, it's really headed into off topic territory.
FTR, I've been playing with Rust, tauri and yew... the whole space is very cool along with support for wasm tooling. It's just off topic in this space. You may want to post to Hacker News[1] or other more general developer groups. Alternatively, if you wrote an article showing how you can integrate this with say package.json for a node project, or with Deno... that would at least be borderline.
1. https://www.echojs.com/about
2. https://news.ycombinator.com/
I'm not the one that downvoated, but there has been a lot of posts on this Snap Camera Server and related topics the past week, and some may be a bit overloaded and/or uninterested, then offput by the posting volume.
This is very conceptual and kind of OT... but leaving it here.
I'd thought of doing similar, by having a websocket channel and a state manager similar to Redux that simply received actions (dispatched from FE), then the state changes delivered as a stream of JSON Diffs.
One step further could be including the UI structure instead of state... though not sure if this would be very well performing at all, since that's what HTML itself represents. It's effectively what Blazor does with the server round trip configuration, and with any kind of latency it's pretty painful in practice.