Clear the act() and ts-jest deprecation warnings from test runs

[alex-rawlings-yyc]

Test runs emitted two classes of warning. Neither failed the build, but both are noise that trains readers to skim CI output, and one is on a path to breaking.

act() warning

React's test renderer warns when a component's state updates outside an act() scope, because updates applied after a test's assertions can't be observed by them — the test passes on a render that was already stale. @testing-library/react wraps render and userEvent in act() automatically, so the warning surfaces only when an update lands outside anything the library wrapped.

SaveAsProjectModal.test.tsx's "prefills the name and description fields from the defaults" was the only test in the file that rendered and asserted entirely synchronously. Its siblings all await something (waitFor or userEvent), which incidentally holds an act() scope open long enough for useProjectsForSource's mocked sendCommand to settle inside it. This one didn't, so the load resolved after the test body finished and fired two state updates — setProjects and setIsLoading — with no act() scope active. Hence exactly two warnings.

Fixed by awaiting the first assertion so the load settles before the test ends.

Considered mocking the hook instead and rejected it: useProjectsForSource has no dedicated test file, and its 100% coverage comes entirely from the two modal tests exercising it for real. Mocking would delete that coverage and require writing a replacement hook test — significant work to fix what one await fixes. Every hook this repo does mock has its own test file; this one doesn't fit the pattern.

ts-jest deprecation

The "ts-jest" config option "isolatedModules" is deprecated and will be removed in v30.0.0

Moved to tsconfig: { isolatedModules: true } — inline compiler options on the transform. Deliberately not hoisted into tsconfig.json as the warning text suggests, since that would scope the flag beyond Jest and cost lint:typecheck its cross-file type-check.

Verified the transpile-only behavior that jest.config.ts depends on still holds: ran the suite from a git worktree, where typeRoots paths like ../paranext-core/lib don't resolve, and confirmed no TS2307 cascade.

Verification

npx jest --ci — 63 suites, 1784 tests passing, 0 act warnings, 0 ts-jest warnings. npm run lint clean.

Note that these warnings only surface when stdout is a TTY or under --ci; Jest suppresses per-suite console blocks when output is piped, which is why they're easy to miss locally.

---

This change is 

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 02d8d0de-19d8-4968-b634-6a8090bc0db7

---

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.}

[imnasnainaec]

@imnasnainaec reviewed 2 files and all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on alex-rawlings-yyc).