fix(testing): do not error when no vite config is found

[jaysoo]

Currently, if you don't have vite.config.ts file in the project, the warning we're trying to log ends up causing an error like this:

 >  NX   Cannot read properties of null (reading 'path')
TypeError: Cannot read properties of null (reading 'path')
    at getSettings (/Users/jack/projects/analog/node_modules/@nx/vite/src/executors/test/vitest.impl.js:101:124)
    at async vitestExecutor (/Users/jack/projects/analog/node_modules/@nx/vite/src/executors/test/vitest.impl.js:55:20)

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 3, 2023 9:23pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• nx affected -t e2e-macos --parallel=1 --base= --head=
• nx affected --target=e2e --base=8dec11ecbe981d82157473647aa038c85705c680 --head=36cbaaf8cbe27a3919d7ce60e9f636d32d5b40cb --parallel=1
• nx affected --target=test --base=8dec11ecbe981d82157473647aa038c85705c680 --head=36cbaaf8cbe27a3919d7ce60e9f636d32d5b40cb --parallel=1
• nx affected --target=build --base=8dec11ecbe981d82157473647aa038c85705c680 --head=36cbaaf8cbe27a3919d7ce60e9f636d32d5b40cb --parallel=3
• nx run-many -t check-imports check-commit check-lock-files depcheck --parallel=1 --no-dte
• nx affected --target=lint --base=8dec11ecbe981d82157473647aa038c85705c680 --head=36cbaaf8cbe27a3919d7ce60e9f636d32d5b40cb --parallel=3
• nx-cloud record -- nx format:check --base=8dec11ecbe981d82157473647aa038c85705c680 --head=36cbaaf8cbe27a3919d7ce60e9f636d32d5b40cb
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

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