Skip to content

chore: update dependencies and dev tooling#35

Merged
michellepace merged 8 commits into
mainfrom
chore/update-deps
Mar 30, 2026
Merged

chore: update dependencies and dev tooling#35
michellepace merged 8 commits into
mainfrom
chore/update-deps

Conversation

@michellepace

Copy link
Copy Markdown
Owner

Summary

  • Update all minor and patch dependencies across the project
  • Update markdownlint-cli2 to v0.22 and disable new MD060 rule (table column style)
  • Update major dependencies: TypeScript 5 → 6, @vercel/analytics 1 → 2, @vercel/speed-insights 1 → 2, jsdom 28 → 29
  • Migrate @vitejs/plugin-react from v5 to v6 (Babel removed in favour of Oxc; React Compiler now uses @rolldown/plugin-babel with reactCompilerPreset())
  • Update commit and CodeRabbit command templates, add Ref MCP server configuration

Test plan

  • npm run check — Biome lint and TypeScript typecheck pass
  • npm run lint:md — Markdown linting clean (0 errors)
  • npm run test:unit — Vitest unit tests pass (4/4)
  • npm run test:e2e — Playwright E2E tests pass (2/2, Chromium + Mobile Safari)
  • npm run build — Production build compiles and generates static pages
  • Manual smoke test — dev server renders, browser console clean

🤖 Generated with Claude Code

michellepace and others added 6 commits March 30, 2026 11:02
commit.md:

- Add $ARGUMENTS support for ad-hoc instructions
- Add recent commit log to context gathering
- Rename `feature:` prefix to `feat:` (conventional commits)
- Tighten template placeholders and rules wording

coderabbit.md:

- Use comment ID in output filename to support multiple evaluations
- Add GitHub reply workflow with safety guard

Templates carried over from my-claude-marketplace where they
were refined through use. Both commands are now clearer and
more practical.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds Ref documentation lookup MCP server (api.ref.tools) to the
project. Requires API_KEY_MCP_REF environment variable.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Dependencies:

- Bump next 16.1.6 → 16.2.1, biome 2.3.14 → 2.4.9,
  tailwindcss/postcss 4.1.18 → 4.2.2, vitest 4.0.18 → 4.1.2
- Bump playwright 1.58.1 → 1.58.2, jsdom 28.0.0 → 28.1.0,
  vite-tsconfig-paths 6.0.5 → 6.1.1, lefthook 2.1.0 → 2.1.4
- Bump type definitions: @types/node, @types/react, @types/react-dom
- Update biome.json schema to 2.4.9

README:

- Add Next.js row to the "What's Installed?" table
- Expand UI component guidance with shadcn, Tailwind Plus, HeroUI
- Switch numbered list to (1)/(2)/(3) format

All quality checks (lint, typecheck, build) and tests (unit, e2e)
pass with the updated dependencies.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bumps markdownlint-cli2 from 0.20 to 0.22. The new MD060 rule
(table-column-style) flags 34 errors across existing compact tables.
Disabled the rule rather than reformatting — compact tables are the
preferred style in this project.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Dependencies:

- typescript ^5.9.3 → ^6.0.2
- @vercel/analytics ^1.6.1 → ^2.0.1
- @vercel/speed-insights ^1.3.1 → ^2.0.0
- jsdom ^28.1.0 → ^29.0.1

Zero-breakage major bumps grouped together. Lint, typecheck,
and unit tests all pass without changes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Migration:

- @vitejs/plugin-react ^5.2.0 → ^6.0.1
- Add @rolldown/plugin-babel ^0.2.2 (new dependency)
- Rewrite vitest.config.ts to use new reactCompilerPreset() API

v6 removes built-in Babel support since Vite 8+ uses Oxc for React
Refresh transforms. React Compiler now requires a separate
@rolldown/plugin-babel plugin with the exported reactCompilerPreset().

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Mar 30, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
nextjs-base Ready Ready Preview, Comment Mar 30, 2026 9:54am

@coderabbitai

coderabbitai Bot commented Mar 30, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a4a85531-105d-4e24-9616-1a37a0223302

📥 Commits

Reviewing files that changed from the base of the PR and between e2ebe43 and 6bde017.

📒 Files selected for processing (2)
  • .claude/commands/coderabbit.md
  • README.md

Summary by CodeRabbit

  • New Features

    • Added richer CodeRabbit comment context and a confirmation step before posting replies on GitHub.
  • Updates

    • Added new MCP server integration "Ref".
    • Setup instructions now list UI options (shadcn/ui, Tailwind Plus, HeroUI v3) and updated framework/language versions.
    • Upgraded core dependencies including Next.js and TypeScript; tooling bumps.
  • Documentation

    • Refined commit message guidelines and added guidance for replying to CodeRabbit.
    • Relaxed markdown table styling lint rule.

Walkthrough

Documentation and configuration updates: CodeRabbit comment output and reply instructions adjusted; commit-message template and workflow refined; linting rule disabled; new MCP server added; Biome schema and numerous npm dependency versions bumped; Vite/Vitest plugin setup changed; README UI/setup instructions updated.

Changes

Cohort / File(s) Summary
CodeRabbit & Commit command docs
.claude/commands/coderabbit.md, .claude/commands/commit.md
Coderabbit fetch now writes combined “Diff context + Comment” to x_coderabbit_COMMENT_ID.md and updates reply workflow with gh api example + confirmation; commit template accepts argument-hint, reorders rule application, adds git log --oneline -4, renames prefixes (feature:feat:) and tightens wording/wrapping guidance to 80–90 chars.
MCP & Tooling configs
.mcp.json, biome.json, vitest.config.ts, biome.json
Added Ref MCP server (http, https://api.ref.tools/mcp, header x-ref-api-key: ${API_KEY_MCP_REF}); bumped Biome schema to v2.4.9; split Vite React plugin use into react() plus @rolldown/plugin-babel invocation in test config.
Linting rules
.markdownlint.yaml
Disabled MD060 (table column style) lint rule.
Project README / setup
README.md
Reworked UI install step into three Tailwind 4–compatible options, adjusted step numbering, added Framework row (Next.js 16.2.1) and bumped TypeScript entry to v6.
Dependencies
package.json
Bumped many deps/devDeps (Next.js →16.2.1, TypeScript →6.0.2, @vercel/, @biomejs/biome, Playwright, Tailwind tooling, vitest, jsdom, types/, added @rolldown/plugin-babel).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐇 I nibble diffs and stitch the thread anew,

Writing comments with context, crisp and true.
Bumps and schemas, plugins in a row—hip-hop—
I hop, I patch, then sprinkle rocket-hop.
A tiny rabbit cheers: build, run, and go!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarises the primary change: updating dependencies and development tooling across the project, which is reflected in all file changes.
Description check ✅ Passed The description is directly related to the changeset, providing clear details about dependency updates, configuration changes, and test results.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-deps

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.claude/commands/coderabbit.md (1)

9-9: ⚠️ Potential issue | 🟠 Major

Document how to derive PULL_NUMBER before the reply command.

The new reply flow requires PULL_NUMBER, but the fetch step only asks to extract owner/repo/comment ID. As written, the reply command is incomplete for users following this file literally.

Suggested doc patch
-Parse `$1` to extract owner, repo, and comment ID.
+Parse `$1` to extract owner, repo, pull number, and comment ID.
 To reply to a PR review comment, use `in_reply_to` on the pull comments endpoint:
 
 ```bash
 gh api repos/OWNER/REPO/pulls/PULL_NUMBER/comments \
   -f body="@coderabbitai ..." \
   -F in_reply_to=COMMENT_ID
</details>


Also applies to: 51-57

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @.claude/commands/coderabbit.md at line 9, Update the coderabbit.md docs to
explicitly show how to derive PULL_NUMBER and add it to the reply command flow:
extend the fetch step that currently parses owner/repo/comment ID to also
explain how to obtain the PR number (PULL_NUMBER) for the target review comment,
and update the example reply invocation (the gh api
repos/OWNER/REPO/pulls/PULL_NUMBER/comments call) to include both -F
in_reply_to=COMMENT_ID and -f body="@coderabbitai ..." so readers have a
complete, copy-pasteable command; reference the existing placeholders
PULL_NUMBER, OWNER/REPO, and COMMENT_ID in the text so it's clear how to
substitute values.


</details>

</blockquote></details>

</blockquote></details>
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/commands/coderabbit.md:
- Line 49: Replace the existing phrasing "recommend to skip a fix" with
"recommend skipping" and change "reply back to coderabbit" to "reply to
coderabbit" in the .claude/commands/coderabbit.md content; update any
occurrences of these exact phrases so the sentence reads "...recommend skipping
a fix, offer if the user would like to reply to coderabbit." ensuring
punctuation and capitalization remain consistent.

In @.mcp.json:
- Around line 8-13: The new secret API_KEY_MCP_REF referenced in the Ref config
(header "x-ref-api-key": "${API_KEY_MCP_REF}") must be documented and validated:
add documentation to the repo README/SETUP that instructs developers to add
API_KEY_MCP_REF to their environment (local .env or OS-level secret store) and
to the CI secret store with the required scope (read-only API key for
https://api.ref.tools/mcp), and update any workflow templates to reference this
secret; additionally, add runtime validation where the Ref client is initialized
(the code that reads the Ref config/headers) to detect a missing API_KEY_MCP_REF
and fail fast with a clear error message explaining how to set the secret.

In `@README.md`:
- Around line 30-34: Update the “What’s Installed?” table in README.md by
replacing the outdated "TypeScript 5" entry with the current version that
matches package.json (e.g., "TypeScript 6 (>=6.0.2)" or "TypeScript ^6.0.2") so
the table row for Language accurately reflects the project's TypeScript
dependency; locate the table row containing "TypeScript 5" and update the text
to the correct version string.

---

Outside diff comments:
In @.claude/commands/coderabbit.md:
- Line 9: Update the coderabbit.md docs to explicitly show how to derive
PULL_NUMBER and add it to the reply command flow: extend the fetch step that
currently parses owner/repo/comment ID to also explain how to obtain the PR
number (PULL_NUMBER) for the target review comment, and update the example reply
invocation (the gh api repos/OWNER/REPO/pulls/PULL_NUMBER/comments call) to
include both -F in_reply_to=COMMENT_ID and -f body="@coderabbitai ..." so
readers have a complete, copy-pasteable command; reference the existing
placeholders PULL_NUMBER, OWNER/REPO, and COMMENT_ID in the text so it's clear
how to substitute values.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5b764b4b-c3f2-4519-ab8f-c5a1bdf11cd7

📥 Commits

Reviewing files that changed from the base of the PR and between f4cf34d and e2ebe43.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (8)
  • .claude/commands/coderabbit.md
  • .claude/commands/commit.md
  • .markdownlint.yaml
  • .mcp.json
  • README.md
  • biome.json
  • package.json
  • vitest.config.ts

Comment thread .claude/commands/coderabbit.md Outdated
Comment thread .mcp.json
Comment thread README.md
michellepace and others added 2 commits March 30, 2026 13:50
The fetched comment file now prepends the PR diff hunk before the
comment body, giving immediate context for evaluation without needing
to read the referenced file first.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Keeps the "What's Installed?" table accurate after the TS 6 upgrade.
@michellepace michellepace merged commit f622bf7 into main Mar 30, 2026
6 of 7 checks passed
@michellepace michellepace deleted the chore/update-deps branch March 30, 2026 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant