David Desmarais-Michaud

I wanted a way to install this on my system. pkg wasn't working, the npm install instructions wasn't working. I ended up simply using esbuild to bundle the entire application,...

Actually, upon diving back into the code to investigate, I have found the reasoning as to why this is the way it is. Suppose this: ```ts const schema = mz.object({...

And the mechanism is to coerce the object to the correct shape when allowUnknown is true and we need to strip keys, and when it coerces it adds the missing...

I have the correct type being inferred from the keysignature based schema: ```ts { foo: sting; [x: string]: unknown } ``` What is your tsconfig and typescript versions? > But...

that's very odd because if I add this test it passed: ```ts import myzod from '../src' import * as z from '../src' it('default keysignature should be the same as named...

I just published v1.7.4 which I believe should fix the type error, I will test more carefully later when I have more time. but just in case it works properly...

it's actually not strange in the end because that test is testing the equality of those values in JS world. It was the type that was wrong. The default export:...

So, yeah. Certain types or schemas are coercable. A mapped type is by definition coercing a type to another type. Or at least performing some transformation on the data within...

I will try and investigate in the next week or so. Hopefully it will be simple enough to fix but when when tsc changes their depth heuristics it can be...

Doesn't seem to fix the problem unfortunately. Typescript has changed its heuristics such that the Intersection type is now deemed to circularly reference itself. Unfortunately I do not foresee time...