This is not going to be necessary. I have confirmed that we can do all this resolution from our esbuild resolver plugin before vite's depscan plugin sees them.

(I'm not opposed to making the change for purely aesthetic reasons, if we want all our virtual stuff to match under one namespace. But we thought this would be necessary to get vite to respect these as potentially external deps, and that is not correct.)

I have no strong opinion, we have this PR ready and it has the benefit of slightly simplifying the code in shared-internals/src/paths.ts 🤷‍♀️ As you like really, feel free to merge or close.

Discussed with Chris: this PR brings value but we should wait for #2029 because it brings tests regarding dependencies making their way to Vite deps.

@mansona rebased on main :)