fix: widen @arkenv/nextjs React peer range (#1833)

## Summary

Fix the React peer dependency conflict affecting Next.js example
installs.

## Root cause

`@arkenv/nextjs` used the pnpm workspace-only `catalog:` alias for its
published React peer dependency. The resulting npm metadata pinned React
to `19.2.5`, conflicting with projects using React `19.2.8` and causing
`ERESOLVE` during installs.

## Fix

Set the peer dependency to the supported React range:

```json
"react": "^18.2.0 || ^19.0.0"
```

This matches Next.js's supported React range and allows the examples to
resolve successfully.

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>

Author: 3 people

.changeset/widen-nextjs-react-peer.md

@@ -0,0 +1,7 @@
+---
+"@arkenv/nextjs": patch
+---
+
+#### Widen the React peer dependency range
+
+Replace the workspace `catalog:` alias for the published React peer dependency with `"^18.2.0 || ^19.0.0"` so installs are not pinned to a single React version.

packages/nextjs/package.json

@@ -32,7 +32,7 @@
 	"peerDependencies": {
 		"arktype": "^2.1.22",
 		"next": "^13.4.0 || ^14.0.0 || ^15.0.0 || ^16.0.0-0",
-		"react": "catalog:"
+		"react": "^18.2.0 || ^19.0.0"
 	},
 	"exports": {
 		"./shared": {

packages/nextjs/src/script.tsx

@@ -39,6 +39,7 @@ export function ArkEnvScript({
 	return (
 		<script
 			id="arkenv-script"
+			// biome-ignore lint/security/noDangerouslySetInnerHtml: JSON-serialized public env with `<` escaped
 			dangerouslySetInnerHTML={{ __html: scriptContent }}
 		/>
 	);