This PR affects SSR only.

• Support resolveId hooks that coerce bare imports into local module paths.
  For example, the vite-tsconfig-paths plugin.

  • How? After a bare import is resolved by vite:resolve, check if the resolved ID is an absolute path that exists in the project root. If it is, avoid marking it as external (for SSR builds) and return the absolute path.

• Respect ssr.noExternal inside ssrImport

  • Add the createSSRExternalsFilter function, which wraps createFilter from @rollup/plugin-utils
  • Avoid coercing bare imports into absolute paths during import analysis
    • After a bare import is resolved by vite:resolve, check if the resolved ID is an absolute path that exists in the project root. If not, preserve the unresolved id so the ssr.noExternal check in ssrImport can work properly.

• Note that ssrImport will never receive the following specifiers (after this PR is merged):

  • relative path
  • path with /@id/ prefix
  • path with /@fs/ prefix

• Use moduleGraph.getModuleByUrl instead of accessing urlToModuleMap directly, so that bare imports added to ssr.noExternal are normalized first. Otherwise, the module will always be undefined.

  • This issue was reported in Discord here, and I've also experienced it myself.

• Remove the need for unwrapId inside ssrImport

  • How? Stop prepending /@id/ to bare imports inside vite:import-analysis