Support for Zod .meta in Content Collections

[Snugug]

Body

Summary

Support Zod's .meta() (and metada and registries in general) in content collection definitions.

Background & Motivation

Content collection definitions are incredibly powerful and produce very useful structured output in JSON Schema, so useful, in fact, that CMSes like Astro Editor are springing up to provide bespoke editing experiences based on the JSON Schema output. However, the user experience of these generated UIs suffers when the only data that can be used to augment it is .describe. I'd like to see the ability to add custom metadata to fields, like titles, placeholder text, and the like, to let tools build better user experiences off of the config work we're already doing.

Goals

• Allow .meta for a content collection field
• Export the meta registered content with the generated .schema.json
• Optionally add Astro configuration to include built content configuration schema to the public directory to make it available to deployed applications

Example

const monster = defineCollection({
  type: 'content',
  schema: z.object({
    title: z.string(),
    hp: z.number().meta({
      title: 'Hit Points',
      description: 'How much health the monster has'
    })
});

[delucis]

This is a Zod 4 feature right? We're exploring how to support it without breaking folks relying on Zod 3, but aren't 100% sure there's a nice path yet. But it'll come eventually! 😄

[Snugug]

Yes it is a Zod feature. Great to hear! If there's a WIP branch where I can test something I'm happy to!