vitest
Vitest 4 tests pass locally but fail in CI
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 →#GitProxy
9 entries tagged “GitProxy”.
github-actions
Auto-triage GitHub issues with an AI agent and Actions
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 → trusted-publishing
Switching to npm trusted publishers: mind the Node version
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 → vitest
A Vitest toThrow test that misses a JSON.parse error
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 → docker
Docker EACCES: permission denied, mkdir as a non-root user
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 → vitest
Migrating GitProxy's tests from Mocha and Chai to Vitest
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 → debugging
Setting NODE_ENV in npm scripts on Windows
Why "NODE_ENV=test mocha" fails on Windows, and the one-line fix with cross-env.
Read the entry → vitest
From proxyquire to Vitest: fixing "undefined" is not valid JSON
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 → meta
Starting a public debugging log for GitProxy
I've decided to share every debugging session and feature while building GitProxy in the open.
Read the entry →