<@U01VD3V5A4T> <@U02BARYFJQK> Following up from <t...
# contributionsj
Jason Bosco
01/26/2022, 3:42 AM@Harisaran @Robert Schultz Following up from this please meet each other! Wanted to intro you since both of you expressed interest in exploring a Deno version of the JS library
h
Harisaran
01/26/2022, 4:36 AMHey @Robert Schultz 👋
Harisaran
01/26/2022, 4:37 AMYeah sure I am down for contributing to deno library !
r
Robert Schultz
01/26/2022, 12:50 PMGreetings. In the end, since typesense has such a straight forward HTTP API I just made a little deno module for my own personal use that does just what I needed: https://github.com/Sembiance/deno/blob/master/Typesense/Typesense.js
Robert Schultz
01/26/2022, 12:55 PMAs for massaging the official library to support deno, I only took a cursory glance but replacing axios looked to be the biggest bulk of the work.
Ideally we could replace that with deno native fetch(), however deno has been working on full compatibility with NPM modules and hopes to have it usable within the next few months: https://deno.com/blog/deno-in-2021
Robert Schultz
01/26/2022, 1:00 PMSince I just needed some basic typesense functionally for my project, the little module I wrote satisfies my needs. In fact it was so smooth going I quietly wondered if maybe that would a better approach for an initial deno module, just building just a lightweight shim above the entire typesense HTTP API rather than trying to massage the official typescript lib
h
Harisaran
01/27/2022, 4:39 AMCool then! We can create a thin wrapper around the HTTP API @Robert Schultz
r
Robert Schultz
01/28/2022, 2:00 AMLooks like someone has made a deno client based on the official lib: https://github.com/bradenmacdonald/typesense-deno
j
Jason Bosco
01/28/2022, 2:02 AMWoaw, this is pretty awesome!
h
Harisaran
01/28/2022, 3:47 AMAwesome !