[Bug]: Wrong location of __mf__virtual in monorepo

[Xeikim]

Describe the bug

My repository is a monorepo，and the project structure is roughly:

packages
   - vite
       - node_modules
       - vite.config.ts
   - vite
       - node_modules
       - vite.config.ts
   - ...
server
    - createServer.ts

server is used to create a vite service and dynamically start different vite applications based on the access route.

When @module-federation/vite creates __mf__virtual, it looks for node_modules based on process.cwd()

vite/src/utils/VirtualModule.ts

Lines 6 to 15 in 7ccebc8

	const nodeModulesDir = (function findNodeModulesDir(startDir = process.cwd()) {
	let currentDir = startDir;
	while (currentDir !== parse(currentDir).root) {
	const nodeModulesPath = join(currentDir, 'node_modules');
	if (existsSync(nodeModulesPath)) {
	return nodeModulesPath;
	}
	currentDir = dirname(currentDir);
	}

In this case, __mf__virtual will be placed in the node_modules of the server directory, not the node_modules in the packages, leading to potential conflicts

Is it a more reasonable solution to look for node_modules based on root of vite.config instead of process.cwd()

Version

v6.0.6

Reproduction

https://codesandbox.io/p/github/Xeikim/mf-monorepo/main?import=true

Relevant log output

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[gioboa]

Thanks @Xeikim for your report. It seems reasonable to me. This is a great opportunity for a PR. If you move these files manually in the right location, is it working fine?

[Xeikim]

Thanks @Xeikim for your report. It seems reasonable to me. This is a great opportunity for a PR. If you move these files manually in the right location, is it working fine?

thanks for your reply.

I tried to solve it, but encountered some problems: #256

I set the root path in the [configResolved] hook:
https://github.com/Xeikim/vite/blob/f278ee575f9b4edeb9284b9468e3e87d5f9be14c/src/index.ts#L35-L41

The issue
We need virtual module paths when adding entry plugins:
https://github.com/Xeikim/vite/blob/f278ee575f9b4edeb9284b9468e3e87d5f9be14c/src/index.ts#L50-L53
When getHostAutoInitPath() is called (which internally uses VirtualModule.getPath()), the root path hasn't been set yet because the configResolved hook hasn't executed. This leads to incorrect path resolution. Transforming getPath into a dynamic function seems a bit difficult

Questions

• What's the recommended way to handle this kind of initialization timing issue in Vite plugins?
• Should we consider restructuring how virtual module paths are resolved?