Best way to make projectile-run-test-at-point use Vitest

[FredrikMeyer]

Hi,

It seems like jest is hardcoded for frontend projects. I see that I can override projectile-test-at-point-rules, but it would be nice to reuse projectile-test-at-point-jest-name since Vitest is API compatible with jest.

Thanks!

[darekwojciechowski]

You can reuse it — projectile-test-at-point-jest-name is just a function, and the rule is a plain plist, so you only need to swap :command-fn. Nothing about the name extraction is jest-specific.

Define a Vitest command function and rebind the JS/TS modes:

(defun my/test-at-point-vitest-command (file-name test-name)
  (format "npx vitest run %s -t %s"
          (shell-quote-argument file-name)
          (shell-quote-argument test-name)))

(let ((rule '(:node-types ("call_expression")
              :name-fn projectile-test-at-point-jest-name
              :command-fn my/test-at-point-vitest-command)))
  (dolist (mode '(js-ts-mode typescript-ts-mode tsx-ts-mode))
    (setf (alist-get mode projectile-test-at-point-rules) rule)))

vitest run rather than plain vitest matters here — without run it starts in watch mode and your compilation buffer never finishes.

To verify, put point inside a test(...) or it(...) block in a .test.ts file and run M-x projectile-run-test-at-point. The command line shown at the top of the compilation buffer should be npx vitest run <file> -t <name>. Use a prefix arg (C-u) if you want to eyeball the command before it runs.

Note this needs a tree-sitter mode — typescript-ts-mode, not typescript-mode. If you're in the non-ts mode it'll tell you there's no parser in the buffer.

Since Vitest is jest AP two-line difference, avitest rule shipping in the defaults might be worth a PR — the only open question is how projectile would pick between them, probably by looking for vitest.config.* or the devDependency.