Skip to content

Adding WASM support #126

Open
Open
@sxlijin

Description

@sxlijin

First off, thanks djc for your work maintaining not only this crate but throughout the Rust HTTP/TLS ecosystem - your name comes up a lot and it's very much noticed and appreciated :)

We're currently using the gcp-auth crate to power our abstractions around calling LLMs, specifically for GCP Vertex. We've currently hand-rolled our gcp auth code on the wasm side, but I was wondering if it would be possible to eventually update (or contribute such updates to) gcp-auth itself to support wasm-bindgen users (e.g. ourselves).

I think the easiest path to do this would be to swap out hyper for reqwest (which has drop-in compatibility, I think with one feature flag, for the js_sys/web_sys impl), but I see some blockers here:

  • It looks like gcp-auth currently directly depends on hyper, although I'm not clear if there's any specific reason it currently uses hyper directly instead of using reqwest under the hood.
  • It also looks like gcp-auth also directly depends on ring, and that one is for significantly less clear reasons.

Let me know if you think this is a welcome direction, if you have other concerns, and what your thoughts are!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions