#contributions

Collaborative Exploration for Developing Deno Version of JS Library

TLDR Jason united Harisaran and Robert to work on a Deno version of the JS library. Both agreed and explored different possibilities including a thin wrapper around the HTTP API.

Powered by Struct AI
Jan 26, 2022 (24 months ago)
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
03:42 AM
Harisaran Robert 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
Harisaran
Photo of md5-b0606ff89d86624d6908bd3c51445af5
Harisaran
04:36 AM
Hey Robert 👋
04:37
Harisaran
04:37 AM
Yeah sure I am down for contributing to deno library !
Robert
Photo of md5-6384d24e1825271b2c37ad8afa24a899
Robert
12:50 PM
Greetings. 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
12:55
Robert
12:55 PM
As 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
01:00
Robert
01:00 PM
Since 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
Jan 27, 2022 (24 months ago)
Harisaran
Photo of md5-0a64851c07cb0368dcc227212539cc95
Harisaran
04:39 AM
Cool then! We can create a thin wrapper around the HTTP API Robert
Jan 28, 2022 (24 months ago)
Robert
Photo of md5-6384d24e1825271b2c37ad8afa24a899
Robert
02:00 AM
Looks like someone has made a deno client based on the official lib: https://github.com/bradenmacdonald/typesense-deno
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
02:02 AM
Woaw, this is pretty awesome!
Harisaran
Photo of md5-0a64851c07cb0368dcc227212539cc95
Harisaran
03:47 AM
Awesome !

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Typescript Support and Import Issues with Typesense

Ahmad faced trouble with Typesense support for Typescript. Jason assisted by suggesting checks and solutions. Phil suggested modifying the import statement. Ultimately, the issue was resolved with a change from Jason in version `v1.1.2`.

24
25mo

Contributing to project using JS, TS, Go and PHP

Matthew volunteered to contribute to the project using JavaScript, Typescript, Go, and PHP. Jason assigned two tasks, including Laravel integration and nest.js library. hi019 encouraged Matthew to try out the Laravel integration.

2

24
29mo

Typesense-JS Client Types Importation Problem.

Stefan had problems importing types from typesense-JS, causing compiler slowdowns. Jason and Damian provided guidance and agreed to export necessary types from Typesense.ts, improving import speed and reducing compiler checks.

29
22mo

Enhancing Typesense-JS For Improved Cache Management

Jordan requested a way to clear the cache in 'typesense-js' when a new document is added. Jason recommended a work-around and supported Jordan's idea to add a 'clearCache' method. Jordan then submitted a PR for this implementation.

1

10
16mo

Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns

Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.

3

74
10mo