Typesense JS Package Update and Configuration Issue
TLDR Alex misinterpreted comments about masterNode
deprecation in typescript types as a removal of nearestNode
. Kishore Nallan clarified that nearestNode
still exists.

Jun 28, 2022 (15 months ago)
Alex
11:27 AMnearestNode
config is gone. Does that mean i should only use nodes
config? Does that mean my searches will get slower?Kishore Nallan
11:30 AMnearestNode
should still exist. We have not removed it. Can you elaborate what you mean by the config being gone?Alex
11:33 AMmasterNode
inside the typescript types. But that is something else 😄
Typesense
Indexed 2764 threads (79% resolved)
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`.
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.
Troubleshooting TypeScript Error with Typesense
GM experienced an error with Typesense in TypeScript, requiring help to correct the issues. Jason helped propose solutions and adjustments to the code. Ultimately, they were able to resolve the errors and successfully implement a search function.

