fix: SSR import in development can't resolve default import (fix vite…

…js#5706)

packages/vite/src/node/ssr/ssrModuleLoader.ts

@@ -263,23 +263,40 @@ async function nodeImport(
 
   try {
     const mod = await dynamicImport(url)
-    return proxyESM(id, mod)
+    return proxyESM(mod)
   } finally {
     unhookNodeResolve()
   }
 }
 
 // rollup-style default import interop for cjs
-function proxyESM(id: string, mod: any) {
-  const defaultExport = mod.__esModule
-    ? mod.default
-    : mod.default
-    ? mod.default
-    : mod
+function proxyESM(mod: any) {
+  const defaultExport = getDefaultExport(mod)
   return new Proxy(mod, {
     get(mod, prop) {
       if (prop === 'default') return defaultExport
       return mod[prop] ?? defaultExport?.[prop]
     }
   })
 }
+
+function getDefaultExport(mod: any) {
+  if (!('__esModule' in mod)) {
+    // === CJS ===
+    return 'default' in mod ? mod.default : mod
+  } else {
+    // === ESM ===
+    // Unlike CJS, an ESM module can have no default export,
+    // thus we start right away with `mod.default` instead of `mod`.
+    let defaultExport = mod.default
+    const visited = new WeakSet()
+    while ('__esModule' in defaultExport && 'default' in defaultExport) {
+      if (visited.has(defaultExport)) {
+        break
+      }
+      visited.add(defaultExport)
+      defaultExport = defaultExport.default
+    }
+    return defaultExport
+  }
+}