Added documentation for new wrangler types --check flag

Author: NuroDev

src/content/docs/workers/languages/typescript/index.mdx

@@ -129,7 +129,7 @@ Most projects will have existing build and development scripts, as well as some
 }
 ```
 
-We recommend you commit your generated types file for use in CI. Alternatively, you can run `wrangler types` before other CI commands, as it should not take more than a few seconds. For example:
+We recommend you commit your generated types file for use in CI. You can run `wrangler types` before other CI commands, as it should not take more than a few seconds. For example:
 
 <Tabs> <TabItem label="npm">
 
@@ -157,6 +157,36 @@ We recommend you commit your generated types file for use in CI. Alternatively,
 
 </TabItem> </Tabs>
 
+Alternatively, if you commit your generated types file and want to verify it stays up-to-date in CI, you can use the `--check` flag:
+
+<Tabs> <TabItem label="npm">
+
+```yaml
+- run: npx wrangler types --check
+- run: npm run build
+- run: npm test
+```
+
+</TabItem> <TabItem label="yarn">
+
+```yaml
+- run: yarn wrangler types --check
+- run: yarn build
+- run: yarn test
+```
+
+</TabItem> <TabItem label="pnpm">
+
+```yaml
+- run: pnpm wrangler types --check
+- run: pnpm run build
+- run: pnpm test
+```
+
+</TabItem> </Tabs>
+
+This fails the CI job if the committed types file is out-of-date, prompting developers to regenerate and commit the updated types.
+
 ### Resources
 
 - [TypeScript template](https://github.com/cloudflare/workers-sdk/tree/main/packages/create-cloudflare/templates/hello-world/ts)

src/content/docs/workers/wrangler/commands.mdx

@@ -980,6 +980,10 @@ wrangler types [<PATH>] [OPTIONS]
   - Control the types that Wrangler generates for `vars` bindings.
   - If `true`, (the default) Wrangler generates literal and union types for bindings (e.g. `myVar: 'my dev variable' | 'my prod variable'`).
   - If `false`, Wrangler generates generic types (e.g. `myVar: string`). This is useful when variables change frequently, especially when working across multiple environments.
+- `--check` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Check if the generated types at the specified path are up-to-date without regenerating them.
+  - Exits with code 0 if types are up-to-date, or code 1 if types are out-of-date.
+  - Useful for CI/CD pipelines and pre-commit hooks to ensure types have been regenerated after configuration changes.
 - `--config`, `-c` <Type text="string[]" /> <MetaInfo text="optional" />
   - Path(s) to [Wrangler configuration file](/workers/wrangler/configuration/). If the Worker you are generating types for has service bindings or bindings to Durable Objects, you can also provide the paths to those configuration files so that the generated `Env` type will include RPC types. For example, given a Worker with a service binding, `wrangler types -c wrangler.toml -c ../bound-worker/wrangler.toml` will generate an `Env` type like this:
   ```ts