⬆️ chore(docs): upgrade Vocs to 2.7.2

[roninjin10]

Summary

• upgrade docs/node from Vocs 1.4.1 to Vocs 2.7.2 and add the required Waku 1.x runtime peer
• migrate the Vocs 1 configuration surface to Vocs 2 (vocs/config, srcDir, top-level theme settings, editLink.link, and codeHighlight)
• preserve the existing Inter typography through Vocs 2's _root.css customization path
• update the landing page to Vocs 2's root component exports, HomePage.Button, and current CSS tokens
• remove the legacy reference/bundler.mdx compatibility copy because Vocs 2 normalizes it to the same route as reference/bundler/index.mdx, which made static generation fail with a duplicate route

Breaking changes handled

Vocs 2 is a ground-up rewrite with a different config and filesystem contract. The old root defineConfig export, nested theme/font config, editLink.pattern, markdown.code.themes, and vocs/components entry point are no longer valid. Vocs 2 also defaults pages to src/pages, so this migration explicitly keeps the existing docs/node/pages tree via srcDir: '.'.

The stale edit link was corrected from the old evmts/tevm-monorepo repository and duplicated docs/node/docs/pages path to evmts/tevm/docs/node/pages.

Validation

• npm view vocs version → 2.7.2
• vocs --version → vocs/2.7.2 darwin-arm64 node-v24.18.0
• pnpm install --filter @tevm/node-docs... --frozen-lockfile --offline → Lockfile is up to date, resolution step is skipped; exit 0
• pnpm run build:app → all five Vocs/Waku build environments completed; [ssg] processing static generation...; [prune] removed static-only 63 chunk(s) and 1 asset(s) from server bundle; ✓ 1 file generated in 4504ms; exit 0
• vitest run in docs/node → Test Files 18 passed | 1 skipped (19), Tests 112 passed | 10 skipped (122); exit 0
• git diff --check origin/main...HEAD → clean

Scope and coordination

This branch was rebased after the concurrent feature PRs landed. It does not edit docs/node/pages/api/methods.mdx. The root pnpm-lock.yaml change is unavoidable for the Vocs 2/Waku/Vite dependency graph and was regenerated with the repository-pinned pnpm 10.33.4, then verified frozen.

Upgrade the tevm core docs site at docs/node from Vocs 1.4.1 to the latest 2.x release, resolve breaking migration changes, fix upgrade-exposed breakage, verify the site builds, and open a focused review PR without merging.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a0a4877

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

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

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "@evmts/*" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
node	Ready	Preview	Jul 30, 2026 2:12am
tevm-monorepo-app	Ready	Preview	Jul 30, 2026 2:12am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
tevm-monorepo-tevm	Ignored		Jul 30, 2026 2:12am

[coderabbitai]

Warning

Review limit reached

@roninjin10, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 041a771d-3b21-4869-a5bd-4030fb0defb6

📥 Commits

Reviewing files that changed from the base of the PR and between c1ad08e and a0a4877.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• docs/node/package.json
• docs/node/pages/_root.css
• docs/node/pages/index.mdx
• docs/node/pages/reference/bundler.mdx
• docs/node/vocs.config.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.