fix: widen @arkenv/nextjs React peer range

[yamcodes]

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:

"react": "^18.2.0 || ^19.0.0"

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

[changeset-bot]

🦋 Changeset detected

Latest commit: 0012f3d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@arkenv/nextjs	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

arkenv

npm i https://pkg.pr.new/arkenv@1833

@arkenv/build

npm i https://pkg.pr.new/@arkenv/build@1833

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@1833

@arkenv/cli

npm i https://pkg.pr.new/@arkenv/cli@1833

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@1833

@arkenv/nextjs

npm i https://pkg.pr.new/@arkenv/nextjs@1833

@arkenv/nuxt

npm i https://pkg.pr.new/@arkenv/nuxt@1833

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@1833

commit: 0012f3d

[arkenv-bot]

📦 Bundle Size Report

Package	Size	Limit	Diff	Status
@arkenv/nextjs	1.32 kB	2.93 kB	0.0%	✅
@arkenv/nextjs/shared	1.15 kB	1.46 kB	0.0%	✅
@arkenv/nextjs/server	1.21 kB	1.95 kB	0.0%	✅
@arkenv/nextjs/client	1.21 kB	1.95 kB	0.0%	✅
@arkenv/nextjs/config	3.55 kB	3.91 kB	0.0%	✅

✅ All size limits passed!

[pullfrog]

Important

The range change itself is correct (it matches Next.js 16's own React peer range), but the PR is missing a changeset — without one @arkenv/nextjs will never be version-bumped and the fix will not reach npm consumers.

Reviewed changes — single-commit fix (e580178) touching only packages/nextjs/package.json:35, replacing the react: "catalog:" peer alias (resolved to a single React version in published metadata) with the explicit supported range "^18.2.0 || ^19.0.0".

• Widened @arkenv/nextjs React peer range from a catalog-pinned single version to ^18.2.0 || ^19.0.0.

⚠️ Missing changeset — the fix will not be released

The change is inert unless @arkenv/nextjs is version-bumped. The Changesets release action only bumps packages that carry a changeset, and .changeset/ currently holds no pending changeset files. Merged as-is, the published metadata keeps the old catalog pin and the consumer ERESOLVE this PR targets stays broken — the entire goal of the PR. The sibling @arkenv/nuxt peer-range fix (#1706) shipped exactly this kind of changeset (.changeset/fix-nuxt-peer-dependencies.md, "@arkenv/nuxt": patch).

Technical details

# Add a changeset for the @arkenv/nextjs peer range fix

## Affected sites
- Missing `.changeset/<name>.md` — `.changeset/` currently contains only `README.md` and `config.json`.

## Required outcome
- Add a changeset bumping `@arkenv/nextjs` with `patch` (v0 package, non-breaking fix),
  using an imperative-mood summary, e.g.:

  ```md
  ---
  "@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.
  ```

## Suggested approach
- Run `pnpm changeset`, select `@arkenv/nextjs`, choose `patch`.

## Notes
- Do not reference GitHub issue numbers in the changeset body.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes — incremental delta since the prior Pullfrog review (head c40216c). The only substantive change is the addition of the previously-missing changeset, which resolves the prior review's one blocking concern.

• Added .changeset/widen-nextjs-react-peer.md bumping @arkenv/nextjs with a patch — exactly the changeset the prior review requested, so the peer-range fix will now be version-bumped and reach npm consumers.
• Merged dev into the branch (bringing #1838, a CI-only Vercel CLI change); no overlap with this PR's scope and no changes to packages/nextjs/package.json or .changeset/ from the merge.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}