Closed asciiwhite closed 3 months ago
I had also a Type error in my application, even without setting "verbatimModuleSyntax" to true.
The error in my case was in the method resolveFetch()
of helpers.ts
.
A valid fix for me was updating both Supabase and Typescript to the latest version.
You're right that using TypeScript 5 with verbatimModuleSyntax
enabled will lead to errors. It sounds like it simplifies default typescript elision. This might be useful but I don't think we'll be supporting this just yet though. If you have time do you mind sharing when the flag would be critical?
If you remove the verbatimModuleSyntax
on v2.64.2 there shouldn't be any errors. Going to close the issue for now but feel free to re-open if this is critical for your use and we will revisit.
Thanks!
Bug report
Describe the bug
Using a tsconfig.json with enabled verbatimModuleSyntax causes type check issues.
To Reproduce
Add "verbatimModuleSyntax": true to "compilerOptions" inside your tsconfig.json.
Expected behavior
No type check issues should happen.
System information