Adding missing components from Import section

src/content/docs/workers/wrangler/custom-builds.mdx

@@ -6,6 +6,8 @@ description: Customize how your code is compiled, before being processed by Wran
 
 ---
 
+import { Render, Type, MetaInfo } from "~/components"
+
 Custom builds are a way for you to customize how your code is compiled, before being processed by Wrangler.
 
 :::note
@@ -27,7 +29,7 @@ Custom builds are configured by adding a `[build]` section in your `wrangler.tom
 
   * The directory in which the command is executed.
 
-* `watch_dir` string | string\[] optional
+* `watch_dir` <Type text="string | string\[]" /> <MetaInfo text="optional" />
 
   * The directory to watch for changes while using `wrangler dev`. Defaults to the current working directory.
 

src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx

@@ -8,7 +8,7 @@ head:
     content: Commands - Wrangler v1 (deprecated)
 ---
 
-import { Render } from "~/components";
+import { Render, Type, MetaInfo } from "~/components";
 
 <Render file="wrangler-v1-deprecation" />
 

src/content/docs/workers/wrangler/system-environment-variables.mdx

@@ -6,6 +6,8 @@ description: Local environment variables that can change Wrangler's behavior.
 
 ---
 
+import { Render, Type, MetaInfo } from "~/components"
+
 System environment variables are local environment variables that can change Wrangler's behavior. There are three ways to set system environment variables:
 
 1. Create an `.env` file in your project directory. Set the values of your environment variables in your [`.env`](/workers/wrangler/system-environment-variables/#example-env-file) file. This is the recommended way to set these variables, as it persists the values between Wrangler sessions.