chore(website): add validation libraries support recipe

Author: TheEdoRan

website/docs/getting-started.md

@@ -10,7 +10,7 @@ description: Getting started with next-safe-action version 7.
 - Next.js >= 14 (>= 15 for [`useStateAction`](/docs/execution/hooks/usestateaction) hook)
 - React >= 18.2.0
 - TypeScript >= 5
-- Zod or a validation library supported by [TypeSchema](https://typeschema.com/#coverage)
+- Zod or Valibot or Yup
 :::
 
 **next-safe-action** provides a typesafe Server Actions implementation for Next.js App Router.
@@ -24,20 +24,7 @@ npm i next-safe-action zod
 ```
 
 :::note
-Zod is the default validation library for next-safe-action, because TypeSchema can cause some issues with deployments, so this documentation uses it for that reason. If you know what you're doing, though, you can use your validation library of choice, or even multiple ones at the same time, thanks to the **TypeSchema** package.
-
-To use this feature, you just need to update the import path for the safe client initialization function from:
-```typescript
-import { createSafeActionClient } from "next-safe-action";
-```
-
-to:
-
-```typescript
-import { createSafeActionClient } from "next-safe-action/typeschema";
-```
-
-and install the related [TypeSchema adapter](https://typeschema.com/#coverage).
+Zod is the default validation library for next-safe-action. If you want to use a different validation library, check out the [validation libraries support](/docs/recipes/validation-libraries-support) recipe.
 :::
 
 ## Usage

website/docs/recipes/additional-validation-errors.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 description: Set additional custom validation errors in schema or in action's server code function.
 ---
 

website/docs/recipes/customize-validation-errors-format.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 description: Learn how to customize validation errors format returned to the client.
 ---
 

website/docs/recipes/extend-base-client.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 3
 description: Learn how to use both a basic and an authorization client at the same time in your project.
 ---
 

website/docs/recipes/extend-previous-schema.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 4
 description: Learn how to use next-safe-action with a i18n solution.
 ---
 

website/docs/recipes/form-actions.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 description: Learn how to use next-safe-action with Form Actions.
 ---
 

website/docs/recipes/i18n.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 8
+sidebar_position: 9
 description: Learn how to use next-safe-action with a i18n solution.
 ---
 

website/docs/recipes/upload-files.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 8
 description: Learn how to upload a file using next-safe-action.
 ---
 

website/docs/recipes/validation-libraries-support.md

@@ -0,0 +1,43 @@
+---
+sidebar_position: 2
+description: Use a validation library of your choice with next-safe-action.
+---
+
+# Validation libraries support
+
+Starting from version 6.0.0, and up to version 7.1.3, next-safe-action used [TypeSchema](https://typeschema.com/) to enable support for multiple validation libraries. This has worked pretty well, but caused some issues too, such as the [Edge Runtime incompatibility](/docs/troubleshooting#typeschema-issues-with-edge-runtime) or [lack of support for TypeScript >= 5.5](/docs/troubleshooting#schema-and-parsedinput-are-typed-any-broken-types-and-build-issues).
+
+To solve these issues, next-safe-action v7.2.0 and later versions ship with a built-in modular support for multiple validation libraries, at this time: Zod, Valibot and Yup.
+
+If you used a TypeSchema adapter before, you should uninstall it, since you just need the validation library of your choice from now on.
+
+The configuration is pretty simple. If you use Zod, you don't have to do anything. If you choose to use Valibot or Yup, other than obviously installing the validation library itself, you need to specify the correct validation adapter when you're initializing the safe action client:
+
+
+For Valibot:
+
+```typescript title="@/lib/safe-action.ts"
+import { createSafeActionClient } from "next-safe-action";
+import { valibotAdapter } from "next-safe-action/adapters/valibot"; // import the adapter
+
+export const actionClient = createSafeActionClient({
+  validationAdapter: valibotAdapter(), // <-- and then pass it to the client
+  // other options here...
+});
+```
+
+For Yup:
+
+```typescript title="@/lib/safe-action.ts"
+import { createSafeActionClient } from "next-safe-action";
+import { yupAdapter } from "next-safe-action/adapters/yup"; // import the adapter
+
+export const actionClient = createSafeActionClient({
+  validationAdapter: yupAdapter(), // <-- and then pass it to the client
+  // other options here...
+});
+```
+
+And you're done! You could also do the same thing for Zod, but it's not required right now, as it's the default validation library.
+
+If you want more information about the TypeSchema to built-in system change, there's a dedicated discussion on GitHub for that, [here](https://github.com/TheEdoRan/next-safe-action/discussions/201).

website/docs/safe-action-client/instance-methods.md

@@ -31,15 +31,15 @@ metadata(data: Metadata) => new SafeActionClient()
 schema(schema: S, utils?: { handleValidationErrorsShape?: HandleValidationErrorsShapeFn } }) => new SafeActionClient()
 ```
 
-`schema` accepts an input schema of type `Schema` (from TypeSchema) or a function that returns a promise of type `Schema` and an optional `utils` object that accepts a [`handleValidationErrorsShape`](/docs/recipes/customize-validation-errors-format) function. The schema is used to define the arguments that the safe action will receive, the optional [`handleValidationErrorsShape`](/docs/recipes/customize-validation-errors-format) function is used to return a custom format for validation errors. If you don't pass an input schema, `parsedInput` and validation errors will be typed `undefined`, and `clientInput` will be typed `void`. It returns a new instance of the safe action client.
+`schema` accepts an input schema of type `Schema` or a function that returns a promise of type `Schema` and an optional `utils` object that accepts a [`handleValidationErrorsShape`](/docs/recipes/customize-validation-errors-format) function. The schema is used to define the arguments that the safe action will receive, the optional [`handleValidationErrorsShape`](/docs/recipes/customize-validation-errors-format) function is used to return a custom format for validation errors. If you don't pass an input schema, `parsedInput` and validation errors will be typed `undefined`, and `clientInput` will be typed `void`. It returns a new instance of the safe action client.
 
 ## `bindArgsSchemas`
 
 ```typescript
 bindArgsSchemas(bindArgsSchemas: BAS, bindArgsUtils?: { handleBindArgsValidationErrorsShape?: HandleBindArgsValidationErrorsShapeFn }) => new SafeActionClient()
 ```
 
-`bindArgsSchemas` accepts an array of bind input schemas of type `Schema[]` (from TypeSchema) and an optional `bindArgsUtils` object that accepts a `handleBindArgsValidationErrorsShape` function. The schema is used to define the bind arguments that the safe action will receive, the optional `handleBindArgsValidationErrorsShape` function is used to [return a custom format for bind arguments validation errors](/docs/recipes/customize-validation-errors-format). It returns a new instance of the safe action client.
+`bindArgsSchemas` accepts an array of bind input schemas of type `Schema[]` and an optional `bindArgsUtils` object that accepts a `handleBindArgsValidationErrorsShape` function. The schema is used to define the bind arguments that the safe action will receive, the optional `handleBindArgsValidationErrorsShape` function is used to [return a custom format for bind arguments validation errors](/docs/recipes/customize-validation-errors-format). It returns a new instance of the safe action client.
 
 ## `action` / `stateAction`