The Node process exits via Node APIs when no test files found

[Jinjiang]

Describe the bug

When run Vitest via Node APIs, the Node process will exit when no test files found. What I expect is returning an error object or a special message instead (without the exit of the whole Node process).

Reproduction

https://github.com/Jinjiang/reproductions/tree/vitest-no-test-found-20240618

System Info

System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1
    Memory: 75.66 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.local/share/mise/installs/node/20/bin/node
    Yarn: 1.22.18 - ~/.yarn/bin/yarn
    npm: 10.2.4 - ~/.local/share/mise/installs/node/20/bin/npm
    pnpm: 9.0.6 - ~/Library/pnpm/pnpm
    bun: 1.0.29 - ~/.local/share/mise/installs/bun/latest/bin/bun
  Browsers:
    Safari: 18.0
  npmPackages:
    vite: ^5.3.1 => 5.3.1 
    vitest: ^1.6.0 => 1.6.0

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[AriPerkkio]

The process.exit is coming from here:

vitest/packages/vitest/src/node/core.ts

Lines 485 to 497 in f969fb0

	// if run with --changed, don't exit if no tests are found
	if (!files.length) {
	// Report coverage for uncovered files
	const coverage = await this.coverageProvider?.generateCoverage?.({ allTestsRun: true })
	await this.reportCoverage(coverage, true)
	this.logger.printNoTestFound(filters)
	if (!this.config.watch || !(this.config.changed || this.config.related?.length)) {
	const exitCode = this.config.passWithNoTests ? 0 : 1
	process.exit(exitCode)
	}
	}

I think we should lift all process.exit calls above the startVitest() method.