Stefan Aebischer

`FetchError: invalid json response body ...` can be observed when `response.json()` is called on a response that is not valid json. Both `1.22.22` and `1.23.0-next.16` do currently not catch this...

This PR seems to introduce quite some complexity. With every additional setting the amount of test cases increases exponentially. Even without this PR it is possible to sign up a...

Just out of curiosity i tried to reproduce the issue of accepting unsinged tokens with the default configuration. But could not reproduce it with the default configuration. @p-v-d-Veeken maybe i'm...

Yet another aspect to consider for DX is error handling. With typescript errors in catch are either of type `unknown` or `any` (depending on [`useUnknownInCatchVariables`](https://www.typescriptlang.org/tsconfig#useUnknownInCatchVariables)). We all know that `any`...

@davidmaxwaterman localstorage indeed is used to store and recover the session. Unfortunately the required change to fix your issue in v1 isn't as easy as your above diff. There are...

@naripok there is a workaround for v1, how you can handle this error (for v2 see next comment): ```js async createSupabaseClient() { const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY, { // disable...

@naripok with supbase v2 release candidate (rc branch) you can catch that error and handle it. I amended your POC. Does that fix your issue? ```html Supabase token bug POC...

@naripok the workaround, will only work in v1, it won't work anymore in v2.

@jczacharia [this workaround](https://github.com/typeorm/typeorm/issues/8890#issuecomment-1194519752) might work for you.

A workaround for this issue that does not require any fix is to specify a `JoinColumn` on the `ManyToOne` side and then query the `JoinColumn` directly. ```ts @Entity() export class...