That said, formatters should be run in pre commit hooks anyway.
https://github.com/keplersj/jest-runner-prettier
Or run it through eslint through jest (which is what we do):
https://github.com/jest-community/jest-runner-eslint
https://www.npmjs.com/package/eslint-plugin-prettier
Either way gets you parallelism from jest. Personally I like the approach of using jest for all the "match files and run actions" logic (tests, lint etc) and then eslint for all the kinds of linting and formatting.
We then configure VSCode to lint autofix on save and get a really nice experience.
Alternatively, it’s pretty common to only run prettier on changed files using lint-staged or pretty-quick.