New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve TypeScript compatibility #183
Comments
Yeah, just started using this, and it's unusable in typescript because of the errors. At least for me, Trying to figure out how I can ignore typechecks on this library only. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When using TypeScript > 5.1, there are numerous type check errors, most of which are related to
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type (…)
, but alsoParameter (…) implicitly has an 'any' type.
. My tsconfig.json already includes"skipLibCheck": true
so there is not a lot I can do to work around besides pinning the TS version.Steps to reproduce
Include typesense in a JS project and e.g.
import type { SearchResponse } from "typesense/lib/Typesense/Documents";
. Runtsc
>= 5.2.Expected Behavior
The project compiles without any issues.
Actual Behavior
There are a lot of typescript issues, probably depending on how much typesense interfaces are imported.
Metadata
Typesense Version:
1.7.2
OS:
MacOS 14.1.1
Node 21.2.0
The text was updated successfully, but these errors were encountered: