validator specific exports

[m1212e]

Hi, would it be possible to allow package exports for validator specific imports? In my case I would like to allow a user of my library to pass a validator schema no matter which kind (valibot, zod, typebox) but they might not have installed the other ones. When importing import type { TypeBox } from "@sinclair/typemap" I get an error that valibot cannot be found. Would it be possible to export specific validator modules from the packagejson so I can use dynamic imports with try/catch to check dynamically which one is available?

[sinclairzx81]

@m1212e Hi, sorry for the delay

would it be possible to allow package exports for validator specific imports?

It guess it would be possible to export sub module paths per validator (id need to revisit the module layout for that). Did you have a specific layout in mind? How would you imagine the import scheme to work for sub module paths? If you can provide an idealized import scheme, I can certainly take a look (PR's also welcome)

---

The need for this package to take on 3 validators is a bit awkward tbh, and probably not all that scalable in the long term (it's a lot of overhead for a singular package). An alternative to sub module pathing would be to release separate packages for Zod and Valibot. I guess updates here mostly come down to having a brief discuss on the merits of multiple packages vs sub module paths first, so open to ideas on how to improve the current setup.

Let me know your thoughts
S

[m1212e]

Hey, I did a quick PR #41 with wildcard exports for the specific packages. It might not be the most elegant solution but it does not break any functionality and allows for granular access to the specific converters. By importing only these, the requirement for the unused dependencies is removed.

This would solve my problem satisfactory. Having multiple packages would work too but is not really necessary/would not give a real benefit opposed to one package with correctly configured peer dependencies and package specific imports. For my usecase this would allow me to call the package specific imports and runtime, surrounded by a try catch and doing this from one or multiple packages does not really make a difference. Would look something like this:

const importErrors = [];
	try {
		const { TypeBoxFromZod } = await import(
			"@sinclair/typemap/typebox/typebox-from-zod.mjs"
		);
		convertedSchema = TypeBoxFromZod(schema as any);
	} catch (error: any) {
		importErrors.push(error);
	}
	try {
		const { TypeBoxFromValibot } = await import(
			"@sinclair/typemap/typebox/typebox-from-valibot.mjs"
		);
		convertedSchema = TypeBoxFromValibot(schema as any);
	} catch (error: any) {
		importErrors.push(error);
	}
	try {
		const { TypeBoxFromTypeBox } = await import(
			"@sinclair/typemap/typebox/typebox-from-typebox.mjs"
		);
		convertedSchema = TypeBoxFromTypeBox(schema as any);
	} catch (error: any) {
		importErrors.push(error);
	}

Let me hear what you think!