Tobi Kremer

I was able to fix the `Error: spawn xdg-open ENOENT` error by running Prisma Studio with the environment variable `BROWSER` explicitly set to `none`. Somehow specifying `--browser none` as a...

> @soulchild @nikkhn Are you also seeing the `Segmentation fault` or only the `Error: spawn xdg-open ENOENT`? What OS are you using? Did this use to work for you before?...

You might be on to something here with function overloading being the issue and this could even be related to https://github.com/ecyrbe/zodios/issues/505#issuecomment-1691582056 In every project I'm using Zodios in, I'm eventually...

Hi ecyrbe, I need some time to look over the API spec and see if there's anything we don't want to make public. The error is so sporadic that I'm...

The new version caused even longer delays (10+ seconds) during autocompletion and type hovering with TS eventually just giving up, sometimes showing sporadic and indeterministic errors (excessively deep types, circular...

For now, I any-typed my (route-specific) middlewares to get my application up and running again: ```ts export const myMiddleware = () => (req: any, res: any, next: any) => {...

@ecyrbe We're now seeing (probably) similar problems in the frontend since introducing `getKeyByAlias`: ```ts zodios.getKeyByAlias('user', { params: { uuid: userUUID } }), ``` Adding just this single line to our...

I was able to reproduce the excessive type instantiation problem we were having in our express backend as well. I added a simple reproduction in the [repository](https://github.com/soulchild/zodios-infinite-types-reproduction) I shared with...

FWIW, even after getting rid of all route-specific middlewares I'm still seeing this sporadically: ``` 'router' implicitly has type 'any' because it does not have a type annotation and is...

@ecyrbe May I kindly ask if you've had a chance to take a look at this yet?