Really like this library overall... while it may seem weird using abstractions for browser API use, the abstractions are clean and the use is really close to what one would hand-craft anyway.
While not a huge fan of TS, it takes a lot of extra work, and at the application level the effort isn't always worth it... I will say, as far as library support, it's been pretty valuable to the point where I've been considering moving anything I push to npm in the future being written in TS.
I usually have a dedicated API service for the front end that's more closely tied to the UI/UX, this may call other API's and services behind it, or the database directly. As a project grows, splitting and adding a primary API gateway may be more prudent.
Interesting... but should probably rely on defined and longer symbols over `^` and `#`... also, against using async decode since that stops this from being a drop in replacement for JSON.stringify/parse.
It's not exactly directly comparable... Parcel is probably the first framework like this that's actually got code splitting and asset use working as I'd expect. I know it's using other tools underneath, but it brings new meaning to the phrase "just works" that doesn't include some scss, images etc, which I'm not sure ESbuild supports the "import" references of, or that it will do templating for the html, let alone a dev server with a watch to (re)run the build.
There's also typescript and type checking to consider, for those that use it.
I'll definitely be playing with this as time permits, but I'm not necessarily "all in" on it just yet.