optimizeUniversalDefaults should be a primary setting

[boycce]

What version of Tailwind CSS are you using?

v3.4.17

What build tool (or framework if it abstracts the build tool) are you using?

webpack 5.92.1

What version of Node.js are you using?

v20.0.0

What browser are you using?

Chrome

What operating system are you using?

macOS

Reproduction URL

Setting the following in tailwind.config.js:

export default {
  // ...
  experimental: {
    optimizeUniversalDefaults: true
  }
}

Displays the following warnings:

warn - You have enabled experimental features: optimizeUniversalDefaults
warn - Experimental features in Tailwind CSS are not covered by semver, may introduce breaking changes, and can change at any time.

Describe your issue

After realising there’s no way to silence the experimental warnings when this flag is enabled, it made me think this should actually be a primary setting. Without it, I find it very difficult to read and debug CSS classes in DevTools because of the unnecessary class clutter, and use it for all our projects.

[philipp-spiess]

Hey @boycce! Appreciate this but I've moved it to the discussions forums since it's not really a bug. I recommend updating to v4 though which uses @property instead 👍