client strips last url path segment

While I bet this is not the intended usage, I've come to like libsql for the ability to be hosted (through a proxy of some sorts) on a single subdomain because the clients happily accept a path in the URL. However, this client in particular splits off the last segment, which all others dont. For example, libsql://example.com/some/sub/path causes the proxy to recieve a request at https://example.com/some/sub (or well, a subpath of said url, so https://example.com/some/sub/v2/pipeline or alike).

The other clients don't seem to do this, so I'm just gonna claim it is a bug in this client and not a result of me messing with something proabably not even intended :)

Start by locating the TypeScript client code that parses the libsql:// URL and constructs the request endpoint. Reproduce the example with /some/sub/path, compare the resulting request path with the other clients, and consider the issue done when the full URL path is preserved in the request.