🦋 Changeset detected

Latest commit: 15f7303

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

The latest updates on your projects. Learn more about Vercel for Git ↗︎

size-limit report 📦

• This might make extending the sidebar schema more difficult if people are doing that? IIRC you can’t do z.object({}).strict().extend({ ... }), because the .strict() is already baked in at that point.

Aren't you thinking of transform(), refine() and superRefine() which returns a type with ZodEffects which would require you to use and()? (which would also no longer be true in Zod 4)

Altho, I have to say I've never seen anyone even trying to extend this schema personally so I think the slightly better DX (knowing the index of the sidebar item with an issue is already a good addition imo) makes sense.

Aren't you thinking of transform(), refine() and superRefine() which returns a type with ZodEffects which would require you to use and()? (which would also no longer be true in Zod 4)

IIRC when I last tried, .strict() only applies to the initial object, which means it breaks when extended, for example:

z
	.object({ a: z.string() })
	.strict()
	.extend({ b: z.string() })
	.parse({ a: 'A', b: 'B' })
//  ^ Fails because `b` is not permitted in the initial strict object

Anyway we don’t really support extending the user config now I think about, only frontmatter schema. So should indeed be fine.