Vitest: vi.mocked(...).mockResolvedValue is not a function
Vitest 3 test fails with vi.mocked(...).mockResolvedValue is not a function after restoreAllMocks. Here's how to fix it in one line.
Read the entry →The Log
My field notes from building GitProxy. 12 and counting.
Vitest 3 test fails with vi.mocked(...).mockResolvedValue is not a function after restoreAllMocks. Here's how to fix it in one line.
Read the entry →Bumping Vitest from 3 to 4 turned my git-proxy CI red while local stayed green. Stale node_modules, broken class mocks, and port clashes. Here's how I fixed each.
Read the entry →Build your own GitHub Actions bot that review pull requests with an LLM: PR Description Checker and Security Scanner.
Read the entry →Build a GitHub Actions bot that triages issues and PRs with an LLM: label, dedupe, security-scan, and run it on Claude, GPT, or Gemini. Here's how I did it.
Read the entry →Moving GitProxy's npm publish from a token to OIDC trusted publishers took a few lines, except for one thing that kept failing.
Read the entry →A Vitest test using expect().toThrow() let a JSON.parse SyntaxError escape and fail the run instead of catching it. Here's why, and the fix.
Read the entry →Moving a Git tag to a newer commit takes a force push, or Git rejects it because the tag already exists. Here's how, plus the gotcha that bites teammates.
Read the entry →A containerized Node app failed with EACCES: permission denied, mkdir './.data' after dropping to a non-root user. Here's the cause and the fix.
Read the entry →How to fix all the ESM mocking errors when moving GitProxy's test suite from Mocha, Chai, Sinon and proxyquire to Vitest + TypeScript
Read the entry →Why "NODE_ENV=test" fails on Windows, and the one-line fix with cross-env.
Read the entry →A git-proxy test failed with 'undefined' is not valid JSON after moving from proxyquire to Vitest. Let's look at the cause and how to fix.
Read the entry →I've decided to share every debugging session and feature while building GitProxy in the open.
Read the entry →