Emilio Almansi

this issue is not really related to zod but to the way circular imports work. when you have a circular dependency between two files, the second one to be loaded...

i'd say the standard trick for solving the issue is to just avoid the circular imports (in your case, that would be moving `Severity` into its own file which is...

Hi @sauween Thanks for your report. Could you please share the following? node version set-interval-async version snippet of code causing the issue

You can enable/disable parts of the schema dynamically using `z.lazy`. ```typescript import { z } from 'zod'; const myState = { moreInformation: false, }; const mySchema = z.lazy(() => {...

I can confirm the bug is happening in both Nest 9.x and 10.x Here's a minimum reproduction repo: https://stackblitz.com/edit/nestjs-11572?file=src%2Fmain.ts Steps to reproduce: 1. Open the link above and wait until...

After some investigation, I believe that the issue comes from how the middleware path is being generated from the route info object. Take a look at this test: ```typescript //...

this library is in maintenance mode, only bug fixes and security upgrades will be added going forward

this seems to be due to a misconfigured bundler; if the issue persists feel free to ping here again with more details about how you are running/bundling your code

you can use [superRefine](https://github.com/colinhacks/zod#superrefine) you first define a refinement effect: ```ts const isReasonableDate: z.RefinementEffect["refinement"] = (dateString, ctx) => { const date = new Date(dateString) const future = DateTime.now().plus({ years: reasonableYears...

Nice, will review ASAP. Thanks for your contribution.