New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/next@15.0.0-canary.155, npm/react-dom@19.0.0-rc-206df66e-20240912, npm/react@19.0.0-rc-206df66e-20240912

View full report↗︎

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

My preferred way would be to have a separate @ai-sdk/valibot package for now. I'll look into this tomorrow.

Thank you for your response. I recommend waiting a few days before taking any action, as we are currently trying to standardize a common interface for TS schema libraries. If our ideas are well received by other schema libraries as well as libraries like the Vercel AI SDK, the integration of schema libraries will become much easier and less complicated.

@fabian-hiller do you have a timeline for the standardization? I could also just release the valibot integration now and then update once the standard is out.

We are trying to release a v0 or v1 of the Standard Schema this week. I will keep you posted.

I have not forgotten you. I will probably give you an update in the next few days.

Standard Schema v1 beta and Valibot v1 beta are now available. Below is some pseudocode on how the Vercel AI SDK could implement it. Standard Schema can reduce implementation effort and prevent or minimize vendor lock-in. We will be adding more documentation and examples to the Standard Schema repository soon. Let us know what you think.

import type { StandardSchema, InferOutput } from "@standard-schema/spec";
import { toJsonSchema as valibotToJsonSchema } from "@valibot/to-schema-schema";
import type { JSONSchema7 } from "json-schema";
import { zodToJsonSchema } from "zod-to-json-schema";

export type Schema<OBJECT = unknown> = Validator<OBJECT> & {
  // ...
};

export function standardSchema<T extends StandardSchema>(
  schema: T,
): Schema<InferOutput<T>> {
  let jsonSchema7: JSONSchema7 | undefined;
  if (schema["~vendor"] === "zod") {
    jsonSchema7 = zodToJsonSchema(schema);
  } else if (schema["~vendor"] === "valibot") {
    jsonSchema7 = valibotToJsonSchema(schema);
  } else {
    throw new Error("Unsupported schema vendor");
  }
  return jsonSchema(jsonSchema7, {
    validate: async (value) => {
      const result = await schema["~validate"]({ value });
      if (result.issues) {
        console.warn("Issues", result.issues);
        return { success: false, error: new Error(result.issues[0].message) };
      }
      return { success: true, value: result.value };
    },
  });
}

The main idea is that libraries like the Vercel AI SDK implement Standard Schema to easily support any schema that follows that spec. This simplifies and improves the DX and both sides. Library authors are no longer required to understand and implement a specific schema library, and in the worst case, maintain a bunch of adapters in their own source code. Users, on the other hand, no longer need to wrap their schema in an adapter function to make it compatible.

The Vercel AI SDK could allow JSON schema and standard schema as input for the parameters property. If the input contains a "~standard" key, it can be passed to the standardSchema function to format it to a unified schema interface.

Great initiative on the StandardSchema. This is definitely the way forward as it massively reduces implementation overhead while increasing interoperability.

@fabian-hiller I really like the idea. However, until standard schema supports conversion to JSON schema and potentially OpenAPI schema, it is only a half-way solution for the needs of the AI SDK (tool calling, structured outputs). We would still need dependencies to the json schema converters, which in turn will have dependencies on the libraries. I'll think more about how to apply it to the AI SDK.

Indeed I would assume for JSON export to be next on the task list for standard schema since it's the most universal and would also give an additional incentive for other validation lib authors to use standard schema and get JSON export for free.