[all components] Export CssVars and DataAttributes

[superhooman]

Related to #5242

34 components now export their CssVars/DataAttributes enums publicly

• I have followed (at least) the PR section of the contributing guide.

[pkg-pr-new]

• base-ui-tanstack-start

• vite-css-base-ui-example

  pnpm add https://pkg.pr.new/mui/base-ui/@base-ui/react@5243
  

  pnpm add https://pkg.pr.new/mui/base-ui/@base-ui/utils@5243
  

commit: f25fa28

[code-infra-dashboard]

Bundle size

Bundle	Parsed size	Gzip size
@base-ui/react	🔺+35.2KB(+7.81%)	🔺+5.16KB(+3.53%)

Details of bundle changes

Performance

Total duration: 1,295.14 ms -61.03 ms^(-4.5%) | Renders: 78 ⁽⁺⁰⁾ | Paint: 2,029.67 ms -72.10 ms^(-3.4%)

Test	Duration	Renders
Popover mount (300 instances)	59.13 ms ▼-15.01 ms(-20.2%)	1 (+0)

13 tests within noise — details

---

Check out the code infra dashboard for more information about this PR.

[netlify]

✅ Deploy Preview for base-ui ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f25fa28
🔍 Latest deploy log	https://app.netlify.com/projects/base-ui/deploys/6a57a505b574bd0008385866
😎 Deploy Preview	https://deploy-preview-5243--base-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[superhooman]

So, I tried to just straight up exporting these enums as is

But I have a questions:

• Are we okay with no reexports from derived components like AlertDialog (Dialog) and Autocomplete (Combobox)? Since they use the same enums as underlying components
• Should I place these exports in a separate barrel file? So it looks cleaner in the main one
• Is it even worth it given it increases bundle size? Perhaps we can publish it as a separate package?