Tree shaking doesn't work (Vite + React + MUI)

[fpolic-profico]

Describe the bug

I installed a fresh version of Vite + React (TS). Also added MUI (https://mui.com) and imported a Button component. When I default import the Button, only that module is downloaded in the network tab. However, if I import the Button as named import the whole MUI library is imported. Here are some screenshots:

Default import

Named import

I also tried migrating one of my CRA projects to Vite but ended up rendering a blank page without any errors. There are a lot of index file import/exports there and I suspect, since tree shaking isn't working, those index file somehow caused a dependency cycle which caused the renderer to silently fail. If someone has an idea how I could fix that (if there's something on my end I did wrong) please let me know.

Reproduction

https://stackblitz.com/edit/vite-react-ts-hv4zat

System Info

System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1
    Memory: 152.97 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.15.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
    Watchman: 2021.10.18.00 - /usr/local/homebrew/bin/watchman
Browsers:
    Chrome: 103.0.5060.114
    Firefox Developer Edition: 97.0
    Safari: 15.2
npmPackages:
    @vitejs/plugin-react: ^2.0.0 => 2.0.0 
    vite: ^3.0.0 => 3.0.0

Used Package Manager

yarn

Logs

No response

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.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• 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.

[sapphi-red]

Closing as tree-shaking one is a duplicate of #8237.

There are a lot of index file import/exports there and I suspect, since tree shaking isn't working, those index file somehow caused a dependency cycle which caused the renderer to silently fail.

This sounds like #3033.