fix: don't change the working directory when loading workspace projects

[sheremet-va]

Description

Closes #6706
Fixes #6832

This behaviour is inconsistent with how the CWD works everywhere else (global setup files keep the original one; the plugin callbacks will also keep the original CWD). The team decided to revert it.

We might explore loading projects in a separate process with a different CWD in the future.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	9ba07d2
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/6729e9c6cd7c760008e44869
😎 Deploy Preview	https://deploy-preview-6811--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[unional]

I think setting the cwd to the project folder is the right approach. vite plugins probable expect cwd to be that.

I just experienced something probably related to this.
The tailwindcss+postcss is not able to scan the content:

warn - The `content` option in your Tailwind CSS configuration is missing or empty.
warn - Configure your content sources or your generated CSS will be missing styles.
warn - https://tailwindcss.com/docs/content-configuration

⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
TypeError: Cannot read properties of undefined (reading 'imports')
 ❯ node_modules/.pnpm/vite@5.4.10_patch_hash=xgqt7nmj25gqyng6hwpkq4rvp4_@types+node@22.8.1/node_modules/vite/dist/node/chunks/dep-BWSbWtLw.js:50832:71
 ❯ process.processTicksAndRejections node:internal/process/task_queues:105:5

https://github.com/repobuddy/storybook-addon-vis/actions/runs/11680177019/job/32522639763

where the tailwind.config.js is:

/** @type {import('tailwindcss').Config} */
export default {
	content: ['./src/**/*.tsx'],
	darkMode: 'class',
	theme: {
		extend: {},
	},
	plugins: [],
}

It works when running vitest within the project (testcase/themes in this case),
but fail (no such message) at the root.

[sheremet-va]

This happens because the cwd was changed during the config resolution and then reverted back because projects are initiated i. the same process.

Plugins may reference cwd in hooks and it will be different from the one that the plugin was initiated with.

To fix your issue, cwd needs to always be the same which this PR achieves.

[hi-ogawa]

Do we have root for browser server? It looks like we enforce it for workspace server, but it appears missing here.

vitest/packages/browser/src/node/index.ts

Line 41 in 9ba07d2

const vite = await createViteServer({

vitest/packages/vitest/src/node/workspace.ts

Lines 71 to 73 in 9ba07d2

	const config: ViteInlineConfig = {
	...options,
	root,

[sheremet-va]

Do we have root for browser server? It looks like we enforce it for workspace server, but it appears missing here.

I don't think it should be specified there because it will override user root, although it should always be the same as the project since the config is the same 🤔

Anyway, let's do this in a separate PR.

[unional]

I think 2.1.5 is indeed breaking. Now the storybook integration crashes:

> vitest


⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
SB_CORE-SERVER_0006 (MainFileMissingError): No configuration files have been found in your configDir: /<repository-root>/.storybook.
Storybook needs a "main.js" file, please add it.

it should be looking at /<project-root>/.storybook

[sheremet-va]

I think 2.1.5 is indeed breaking. Now the storybook integration crashes:

> vitest


⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
SB_CORE-SERVER_0006 (MainFileMissingError): No configuration files have been found in your configDir: /<repository-root>/.storybook.
Storybook needs a "main.js" file, please add it.

it should be looking at /<project-root>/.storybook

This is intentional. process.cwd() always equals the working directory from where vitest was running even in different workspace projects. While it makes running vitest from different folders behave differently, it is more consistent during the run (cwd in config() hook is the same as cwd in transform() hook). To support different cwd, we need to spawn child_process for every project which is out of scope for now

[ivancuric]

This change breaks testing in my monorepo setup. Previously I could test via the workspace both in the monorepo root task (single process) and via the VScode plugin, now I can only run tests from each package directory in its own process.

Some of the packages have build artifacts which aren't importable and need to be moved to other packages' /public directories during the buildStart hooks. For that I require the cwd to work as I need to resolve the dependent packages.

For now I'll rely on turborepo's task spawning and skip the VScode extension.

[unional]

To me, this completely broke workspace support. I'm waiting for a working solution before I try the workspace feature again.