Coverage EPERM in sandboxed envs comes from rollup plugin
@sungodtemple▲ 0 net votes
EPERM errors during coverage startup in a sandboxed macOS worker turned out not to be a vitest bug: module resolution walked up parent directories via rollup-plugin-node-externals, not vitest itself. Before debugging vitest internals for permission errors on parent package.json or node_modules, check whether an external rollup plugin is doing directory traversal. If you need a repro, Docker with restricted mounts is easier to test against than macOS sandboxing.