zod-transform-socials needs to be upgraded to zod 4 to be compatible with Astro 6.0

[enigmalea]

Several zod schemas were updated in the release of Zod 4 including z.string().url() -> z.url() leading to breaking changes.

[essential-randomness]

Was it compatible before? (asking cause I just published an update, unsure if I broke it or it's a separate issue)

[enigmalea]

Prior to Astro 6.0, Astro used Zod 3. With Astro 6.0 they made a breaking change to Zod 4.

So when I went to upgrade today I updated my own schemas without thinking about SocialLinks. When I went to run, I received an error related to the links portions of my mod content collection where I use the SocialLinks schema in relation to Zod 4.

[enigmalea]

It looks like this is an Astro enforcement and not a Zod one., so the types still exist for now. I'm not planning on removing the old definitions entirely. Going to look into supporting both.

ETA: could we just define unions? This was my instinctive thought but I second guessed myself.

export const SocialsSchema = z.union([
  z.union(z.string().url(), z.url()),
  z.object({
    icon: z.string().optional(),
    platform: z.string().optional(),
    url: z.union(z.string().url(),z.url()),
    username: z.string().optional(),
  }),
]);

[enigmalea]

Was it compatible before? (asking cause I just published an update, unsure if I broke it or it's a separate issue)

Oh no. This was just funny timing. You released at the same time I was upgrading. It wouldn't have worked with 6.0 either way. lol

[essential-randomness]

Yeah, I encountered this issue with at least another one of the plugins here. I forget which one and I failed to solve it, but I may try again because I also need to update stuff to Astro 6.

[enigmalea]

Yeah, I encountered this issue with at least another one of the plugins here. I forget which one and I failed to solve it, but I may try again because I also need to update stuff to Astro 6.

HUGE FYI when you update FujoCoded stuff to Astro 6, astro-icons is causing memory issues with Astro 6 because of the new way Vite 7 loads resources, but only on Windows. If the FujoVerse sites aren't already, they will need to include ONLY the icons that are being used from the icon sets.

It took me most of the weekend to figure out this memory issue so I could attempt to test updates to the plugin. 😭

I did do some other research though in between my moments of frustration and found that due to the way zod ships their own updates, we may have to leave legacy Astro support on a separate branch, and begin Astro 6 support on a new one. I'll let you know if I can't discover a way to do it programmatically.