chore: drop unused @fast-check/vitest devDependency

[ndycode]

Summary

• Removes the @fast-check/vitest devDependency. Nothing in the repository imports it — the only references anywhere are the package.json entry, its lockfile subtree, and a line in the historical audit evidence snapshot.

What Changed

• npm uninstall @fast-check/vitest: one line out of devDependencies, 63 lines out of package-lock.json.
• Plain fast-check stays: the property suites (test: property-check the unsupported-model fallback invariants #574, test: property-check write-queue serialization and clamp invariants #575, fix: deduplicateAccounts fixpoint loop and identity property tests #579) deliberately use fc.assert/fc.asyncProperty with explicit vitest imports per repo convention, so the test.prop wrapper this package provides has no consumers.
• typescript-language-server (the other knip-flagged devDependency) was deliberately left alone — editor/LSP tooling usage is invisible to import scans, so that removal is a maintainer call.

Validation

• npm run typecheck after the uninstall
• Spot-check test run (test/settings-panels.test.ts) confirms the install is healthy
• grep -r "@fast-check/vitest" across the repo (excluding node_modules/dist): only package.json/lockfile and the frozen audit evidence file

Docs and Governance Checklist

• No user-visible behavior, commands, settings, or docs affected (devDependency only; not part of the shipped tarball)

Risk and Rollback

• Risk level: minimal — unused devDependency; cannot affect runtime or the published package.
• Rollback plan: npm install -D @fast-check/vitest restores it.

Additional Notes

• If property tests ever migrate to the test.prop API, reinstalling is a one-liner; until then the dependency is pure surface.

https://claude.ai/code/session_01XNtnkLbBiXZxfQQYLMpucB

---

Generated by Claude Code

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

removes the unused @fast-check/vitest devdependency from package.json and its lockfile subtree. plain fast-check is retained since the property test suites use fc.assert/fc.asyncProperty directly with explicit vitest imports.

• package.json: one-line removal of @fast-check/vitest: ^0.2.4 from devdependencies; fast-check stays.
• package-lock.json: @fast-check/vitest block removed cleanly; a side effect strips the libc field from ~12 @rollup/rollup-linux-* optional platform packages, likely due to npm version differences during lockfile regeneration.

Confidence Score: 4/5

safe to merge — removing an unused devdependency with no runtime or published-package impact.

the @fast-check/vitest removal is clean and well-validated. the only notable artifact is the collateral stripping of libc fields from rollup's linux platform packages, an unintended lockfile diff from npm version drift; those packages are optional so the install won't break, but musl-based ci runners could silently fall back to the wasm rollup.

package-lock.json deserves a quick look for the rollup libc field removals beyond the intended @fast-check/vitest subtree.

Important Files Changed

Filename	Overview
package.json	removes @fast-check/vitest from devDependencies — clean, no consumers in the codebase
package-lock.json	removes @fast-check/vitest lockfile subtree cleanly; also strips libc field from rollup linux platform packages as an unintended side effect of npm version differences

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[npm uninstall @fast-check/vitest] --> B[package.json: remove entry]
    A --> C[package-lock.json: remove @fast-check/vitest block]
    C --> D[expected: fast-check peer dep subtree removed]
    C --> E[unexpected side effect: libc field stripped from @rollup/rollup-linux-* optionals]
    E --> F{impact?}
    F -->|glibc linux / macOS / windows| G[no impact - libc not used]
    F -->|musl linux / Alpine CI| H[npm falls back to wasm rollup - slower builds only]

Loading

Comments Outside Diff (1)

1. package-lock.json, line 951-1124 (link)

   unexpected libc field removals from rollup platform packages

   the uninstall also stripped the libc field from ~12 @rollup/rollup-linux-* entries (both glibc and musl variants for arm, arm64, loong64, ppc64, riscv64, s390x, x64). this suggests the lockfile was regenerated with a different npm version than the one that originally wrote it — the libc field is used by npm to select the correct native binary on linux. since these packages are optional: true and their names already encode the variant (-gnu vs -musl), practical impact is low. on an alpine/musl ci runner the wrong binary could theoretically be selected, falling back to the wasm rollup, which just makes builds slower. worth noting the npm version in use if this diff looks unexpected.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: package-lock.json
   Line: 951-1124
   
   Comment:
   **unexpected `libc` field removals from rollup platform packages**
   
   the uninstall also stripped the `libc` field from ~12 `@rollup/rollup-linux-*` entries (both `glibc` and `musl` variants for arm, arm64, loong64, ppc64, riscv64, s390x, x64). this suggests the lockfile was regenerated with a different npm version than the one that originally wrote it — the `libc` field is used by npm to select the correct native binary on linux. since these packages are `optional: true` and their names already encode the variant (`-gnu` vs `-musl`), practical impact is low. on an alpine/musl ci runner the wrong binary could theoretically be selected, falling back to the wasm rollup, which just makes builds slower. worth noting the npm version in use if this diff looks unexpected.
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
package-lock.json:951-1124
**unexpected `libc` field removals from rollup platform packages**

the uninstall also stripped the `libc` field from ~12 `@rollup/rollup-linux-*` entries (both `glibc` and `musl` variants for arm, arm64, loong64, ppc64, riscv64, s390x, x64). this suggests the lockfile was regenerated with a different npm version than the one that originally wrote it — the `libc` field is used by npm to select the correct native binary on linux. since these packages are `optional: true` and their names already encode the variant (`-gnu` vs `-musl`), practical impact is low. on an alpine/musl ci runner the wrong binary could theoretically be selected, falling back to the wasm rollup, which just makes builds slower. worth noting the npm version in use if this diff looks unexpected.

_{Reviews (1): Last reviewed commit: "chore: drop unused @fast-check/vitest de..." | Re-trigger Greptile}

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[coderabbitai]

Warning

Review limit reached

@ndycode, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 minute and 52 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8b74ce37-da8d-4cd8-8d7e-0ce58a1df88c

📥 Commits

Reviewing files that changed from the base of the PR and between b566656 and 025dc13.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/audit-62-drop-unused-fastcheck-vitest

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/audit-62-drop-unused-fastcheck-vitest

---

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 and usage tips.}