linked package's .mjs files cannot be externalized via test.server.deps.external

[hi-ogawa]

Describe the bug

For the issue #6543, I was suggesting to externalize monorepo packages, but while testing it out, I noticed .mjs outside of node_modules is currently inlined due to extraInlineDeps

vitest/packages/vitest/src/constants.ts

Lines 8 to 13 in 2a50464

	export const extraInlineDeps = [
	/^(?!.*node_modules).*\.mjs$/,
	/^(?!.*node_modules).*\.cjs\.js$/,
	// Vite client
	/vite\w*\/dist\/client\/env.mjs/,
	]

Since Vite-node matches options.inline before options.external, it doesn't look possible to externalize linked package's .mjs.

vitest/packages/vite-node/src/externalize.ts

Lines 119 to 124 in 2a50464

	if (matchExternalizePattern(id, moduleDirectories, options?.inline)) {
	return false
	}
	if (matchExternalizePattern(id, moduleDirectories, options?.external)) {
	return id
	}

Is there any way to achieve this? It looks like this might be desired in some case though not many. If we check options.external before options.inline, then that would allow it but not sure how breaking this change would be.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-tq3er6?file=vite.config.ts

With a package exporting linked-dep/good.js and linked-dep/bad.mjs, using test.server.deps.external: [/\/linked-dep\//] externalizes only linked-dep/good.js. Here is a log from DEBUG=vite-node:* vitest:

  vite-node:client:native /home/projects/vitest-dev-vitest-tq3er6/linked-dep/good.js +5ms
  vite-node:server:request /linked-dep/bad.mjs +24ms
  vite-node:client:execute /home/projects/vitest-dev-vitest-tq3er6/linked-dep/bad.mjs +21ms

System Info

(stackblitz)

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 2.1.1 
    vite: latest => 5.4.7 
    vitest: latest => 2.1.1

Used Package Manager

npm

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.