Sync open source content 🐝 (from b28b3c80dff233df1eb6ba77ff3e597ed5ec700c)

Author: beezythebot

docs/customize/typescript/react-hooks.mdx

@@ -120,27 +120,27 @@ Before using React Hooks, you need to install their dependencies and configure y
 
 ### Install required dependencies
 
-The generated SDK with React Hooks has TanStack Query and Zod dependencies that should be listed in the SDK's `package.json`. However, you might need to install them explicitly in your application:
+The generated SDK with React Hooks has TanStack Query as a dependency that should be listed in the SDK's `package.json`. Zod is bundled with the SDK. However, you might need to install TanStack Query explicitly in your application:
 
 <CodeWithTabs>
 ```bash !!tabs npm
-npm install @tanstack/react-query zod
+npm install @tanstack/react-query
 ```
 
 ```bash !!tabs yarn
-yarn add @tanstack/react-query zod
+yarn add @tanstack/react-query
 ```
 
 ```bash !!tabs pnpm
-pnpm add @tanstack/react-query zod
+pnpm add @tanstack/react-query
 ```
 
 </CodeWithTabs>
 
 <Callout title="Note">
-  The Speakeasy-generated TypeScript SDK uses Zod for runtime type validation,
-  and TanStack Query powers the React hooks. These dependencies are required for
-  the SDK to function correctly.
+  The Speakeasy-generated TypeScript SDK bundles Zod for runtime type validation,
+  and TanStack Query powers the React hooks. TanStack Query is required for
+  the React hooks to function correctly.
 </Callout>
 
 ### Set up the React Query provider

docs/languages/typescript/methodology-ts.mdx

@@ -326,11 +326,11 @@ export namespace DrinkOrder$ {
 ```
 
 <Callout title="Note" type="info">
-It's important to note that Zod is a peer dependency.
+Zod is bundled as a regular dependency in Speakeasy TypeScript SDKs.
 
-The reason for listing Zod as a peer dependency is to use the user's installation of Zod if they have it. Every popular package manager, except for Yarn, says, &quot;If the user doesn't have a peer dependency installed, I'm gonna go ahead and install it and make it available&quot;.
+Speakeasy moved Zod from a peer dependency to a regular dependency to address Zod v4 runtime errors. This ensures the SDK always uses its own bundled Zod v3 even if the customer is using Zod v4, preventing version conflicts.
 
-Why does Speakeasy use peer dependencies? There are situations where the `node_modules` tree ends up with multiple Zod versions if the user has a different version of Zod installed than what the SDK requires. For example:
+Previously, there were situations where the `node_modules` tree could end up with multiple Zod versions if the user had a different version of Zod installed than what the SDK required. For example:
 
 ```text
 node_modules/
@@ -340,7 +340,7 @@ node_modules/
       zod/ v3.23.5
 ```
 
-If the SDK throws a Zod validation error, the user might have code like this:
+If the SDK threw a Zod validation error, the user might have code like this:
 
 ```typescript
 import { Sdk } from "sdk";
@@ -360,9 +360,9 @@ try {
 }
 ```
 
-The code at `branch 1` will not evaluate to `true` because the runtime loaded the wrong `ZodError` version. Using peer dependencies helps prevent this Zod validation error.
+The code at `branch 1` would not evaluate to `true` because the runtime loaded the wrong `ZodError` version. By bundling Zod as a regular dependency, Speakeasy prevents this validation error and ensures consistent behavior.
 
-Speakeasy SDKs wrap `ZodError`s with a custom error type declared in each SDK. In practice, the Zod error is hidden from users and gets them to only work with the error type exported from the SDK. In the future, we start listing Zod as a direct dependency and are unaware of other Zod installations the user might have.
+Speakeasy SDKs wrap `ZodError`s with a custom error type declared in each SDK. In practice, the Zod error is hidden from users and gets them to only work with the error type exported from the SDK.
 
 </Callout>
 

guides/sdks/typescript-monorepo-tips.mdx

@@ -18,7 +18,9 @@ The most common issue we see is dependency confusion. This happens when develope
 
 ### Why is this a problem?
 
-Let's say a developer have Zod installed in their monorepo's root, and their Speakeasy SDK also uses Zod. They might run into a situation where code like this doesn't work:
+Let's say a developer has Zod installed in their monorepo's root, and their Speakeasy SDK also uses Zod. With Speakeasy's bundled Zod dependency, this is no longer an issue since the SDK uses its own version of Zod v3, preventing conflicts with user installations of Zod v4.
+
+Previously, developers might have run into a situation where code like this didn't work:
 
 ```typescript
 try {
@@ -28,13 +30,13 @@ try {
   });
 } catch (err) {
   if (err instanceof ZodError) {
-    // 🚨 This check fails!
+    // This check could fail with peer dependencies!
     console.log("Validation error:", err.errors);
   }
 }
 ```
 
-The `instanceof` check fails because they're importing `ZodError` from a different instance of Zod than what the SDK is using. It's the same code, but JavaScript treats them as different classes.
+The `instanceof` check could fail because they were importing `ZodError` from a different instance of Zod than what the SDK was using. By bundling Zod, Speakeasy eliminates this confusion.
 
 ### How to fix it
 

openapi/frameworks/elysia.mdx

@@ -999,13 +999,7 @@ In the SDK `README.md` file, you'll find the documentation for your Speakeasy SD
 
 Note that the SDK is not ready for production use. To get it production-ready, follow the steps outlined in your Speakeasy workspace.
 
-The SDK has Zod as a peer dependency, as can be seen in the `sdk-typescript/package.json` file.
-
-Install the required Zod version:
-
-```bash Terminal
-npm i zod
-```
+The SDK includes Zod as a bundled dependency, as can be seen in the `sdk-typescript/package.json` file.
 
 Replace the code in the `src/main.ts` file with the following example code taken from the `sdk-typescript/docs/sdk/users/README.md` file:
 

openapi/frameworks/hono.mdx

@@ -939,13 +939,7 @@ Your SDK documentation includes instructions for installing the MCP server.
 
 Note that the SDK is not ready for production use. To get it production-ready, follow the steps outlined in your Speakeasy workspace.
 
-The SDK has Zod as a peer dependency, as can be seen in the `sdk-typescript/package.json` file.
-
-Install the required Zod version:
-
-```bash Terminal
-npm i zod
-```
+The SDK includes Zod as a bundled dependency, as can be seen in the `sdk-typescript/package.json` file.
 
 Replace the code in the `src/main.ts` file with the following example code taken from the `sdk-typescript/docs/sdks/users/README.md` file:
 

openapi/frameworks/nestjs.mdx

@@ -697,13 +697,7 @@ In the SDK `README.md` file, you'll find documentation about your Speakeasy SDK.
 
 Note that the SDK is not ready for production use. To get it production-ready, follow the steps outlined in your Speakeasy workspace.
 
-The SDK has Zod as a peer dependency, as can be seen in the `sdk-typescript/package.json` file.
-
-Install the required Zod version:
-
-```bash Terminal
-npm i zod
-```
+The SDK includes Zod as a bundled dependency, as can be seen in the `sdk-typescript/package.json` file.
 
 Replace the code in the `src/main.ts` file with the following lines of code: