christopher-buss / christopher-buss/jest-roblox-cli
coverage: report writer fails with "No such built-in module ...\lib\text" (also lib\lcov) on the rokit-installed 0.3.22 binary
@christopher-buss is already working on this.
Since Sep 4, 2026.
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 4
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Summary
jest-roblox-cli --coverage instruments and runs the suite fine, but the report step dies before writing anything:
% Coverage report from istanbul
▶ Roblox-TS 1 passed (4 tests)
Test Files 1 passed (1)
Tests 4 passed (4)
Error: No such built-in module: C:\Users\kobie\.rokit\tool-storage\christopher-buss\jest-roblox-cli\0.3.22\lib\text
The path it fails on is <binary dir>\lib\<reporter name>, so it looks like the reporter is resolved relative to the executable instead of from the bundled istanbul reporters. Switching reporters just changes the name:
{ "test": { "coverageReporters": ["lcov", "json-summary"] } }
Error: No such built-in module: C:\Users\kobie\.rokit\tool-storage\christopher-buss\jest-roblox-cli\0.3.22\lib\lcov
No coverage/ directory is created. Same result on 0.3.21.
Environment
- jest-roblox-cli 0.3.22 (also 0.3.21), installed through rokit (
christopher-buss/jest-roblox-cli@0.3.22), so the binary runs from~\.rokit\tool-storage\...\0.3.22\jest-roblox-cli.exe - Windows 11 (10.0.26200), Node 24.15.0
- backend
studio-cli - roblox-ts project on
@isentinel/roblox-ts@4.0.12/ TypeScript 6.0.3,@rbxts/jest+@rbxts/jest-globals3.16.0-ts.1, pnpm 11
jest.config.json
{
"backend": "studio-cli",
"jestPath": "ReplicatedStorage/rbxts_include/node_modules/@rbxts/jest/src",
"rojoProject": "test.project.json",
"luauRoots": ["out"]
}
test.project.json mounts the whole out/ at ReplicatedStorage.__tests.
Steps
rbxtsc
jest-roblox-cli --backend studio-cli --coverage --testPathPattern base/shared/angles
Expected: coverage/ with the text (or lcov) report. Actual: the error above after the test summary, exit code 1.
Everything else works well here — the batched run of 56 spec files / 320 tests and the TS source-mapped failures are great. Happy to test a fix build.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.