fix(css): workaround tsx esModule interop of sass-embedded import

[hi-ogawa]

Description

• Closes sass dynamic import is undefined when building with "modern-compiler" and sass-embedded #19052
• Supersedes fix(css): avoid using default export from sass-embedded #19053
• Related __esModule interop is applied to .cjs files privatenumber/tsx#627

As seen in privatenumber/tsx#627, tsx unwraps named exports for __esModule and thus strips off default export. The issue seems to be acknowledged as node inconsistency bug, but I'm not sure about the plan. Vite side fallback is simple, so probably it's worth having it.

From my quick read through, tsx transforms import(xxx) to unwrap default for __esModule automatically (transform-dynamic-import.ts). This seems to happen for all esm code loaded via tsx (load.ts).

I tested four combinations locally based on https://github.com/hi-ogawa/reproductions/tree/main/vite-19182-sass-tsx

• node + sass-embedded
• node + sass
• tsx + sass-embedded (this was failing before)
• tsx + sass

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/vite@19182

commit: fb54eaf

[bluwy]

I personally prefer to not add special handling here and have it fixed in tsx instead. It looks like it's going to affect more modules that only sass-embedded, and also it's not clear to me why it's mangling the exports of .js files in node_modules.