fix(vite): exit from test if no files found

[AliYusuf95]

Current Behavior

After running nx test project or nx run-many -t test with no test files with @nx/vite:test plugin, vitest process exit directly but nx reporter keep waiting for finish notification which cause to waiting indefinitely.

vitest reference:
https://github.com/vitest-dev/vitest/blob/main/packages/vitest/src/node/core.ts#L409-L413
https://github.com/vitest-dev/vitest/blob/main/packages/vitest/src/node/cli/cli-api.ts#L102-L116

console log example:

nx test project

> nx run project:test


 RUN  v2.0.5 /path/to/project

include: src/**/*.{test,spec}.{js,mjs,cjs,ts,mts,cts,jsx,tsx}
exclude:  **/node_modules/**, **/dist/**, **/cypress/**, **/.{idea,git,cache,output,temp}/**, **/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*
No test files found, exiting with code 0

nx run-many -t test --no-cache -p project

 NX   Running target test for project project

      With additional flags:
        --cache=false

   →  Executing 1/1 remaining tasks...

   ⠹  nx run project:test

Expected Behavior

nx test project should exit directly in case vitest process exit early.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Aug 31, 2024 2:35am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit daa3408. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=18e5535940a0aff86dc845f3714b07b94a0db8d8 --head=daa34085bd53414e41f6fd94a844181b901f18a9 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=18e5535940a0aff86dc845f3714b07b94a0db8d8 --head=daa34085bd53414e41f6fd94a844181b901f18a9
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[HashemKhalifa]

I'm facing the same problem, regardless of passing passWithNoTests: true in the project.json and vite.config.ts

checked out the branch and it solved the problem.

I am still getting into the console from Vitest the following, but not an issue for me

include: src/**/*.{test,spec}.{js,mjs,cjs,ts,mts,cts,jsx,tsx}
exclude:  **/node_modules/**, **/dist/**, **/cypress/**, **/.{idea,git,cache,output,temp}/**, **/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*
No test files found, exiting with code 0

[AliYusuf95]

I'm facing the same problem, regardless of passing passWithNoTests: true in the project.json and vite.config.ts

checked out the branch and it solved the problem.

I am still getting into the console from Vitest the following, but not an issue for me

include: src/**/*.{test,spec}.{js,mjs,cjs,ts,mts,cts,jsx,tsx}
exclude:  **/node_modules/**, **/dist/**, **/cypress/**, **/.{idea,git,cache,output,temp}/**, **/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build,eslint,prettier}.config.*
No test files found, exiting with code 0

exiting with code 0 means it finished successfully, I think it's fine to have it

[HashemKhalifa]

@AliYusuf95 understood, to clarify I have no problem with that at all, my main concern is that it has been stuck when no test is found

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.