Last 12 weeks · 111 commits
4 of 6 standards met
Description Firefox's UA stylesheet already sets , so Preflight's rule overrides that and applies an unwanted auto outline to focused iframes. Adding to the selector preserves the improved focus ring behavior for all other elements while respecting Firefox's native iframe focus styling. Fixes #19795
Reopen issue #20035 As discussed in PR https://github.com/tailwindlabs/tailwindcss/pull/19942, it would be great if the Vite plugin exposed an option to configure polyfills. Currently, when is set and the project targets browsers through Vite instead, there does not seem to be a way to disable Tailwind’s generated polyfills. I’d like to propose adding a option alongside optimize in the Vite plugin configuration. This would allow users to either disable polyfills entirely during compilation, or selectively keep only the ones they need.
What version of Tailwind CSS are you using? v4.0.0 What build tool (or framework if it abstracts the build tool) are you using? What version of Node.js are you using? v20.18.1 What browser are you using? N/A What operating system are you using? Ubuntu 20.04 Reproduction URL N/A Describe your issue** I have the following directory structure: My looks like this: Reason: I only want tailwindcss to scan the php files in the root directory, nothing more, especially nothing in subdirectories. Compiling works: But when I add : Notice how long it takes. And sometimes I get this error: What is it doing in ? It looks like it wants to watch this directory, but why? It isn't added to at all. When I only source a subdirectory () the problem goes away. Is there something broken with setting up the watchers since v4? I had no problems with v3 with the same configuration (through a though, but same/similar pattern only watching in the root dir.).
What version of Tailwind CSS are you using? "tailwindcss": "4.1.18", "@tailwindcss/postcss": "^4.2.2", What build tool (or framework if it abstracts the build tool) are you using? Nx@22.63 Angular@21.2.6 What version of Node.js are you using? 24.10.0 What browser are you using? Not relevant - happens already on an "npm ls" What operating system are you using? Windows Reproduction URL _None_ Describe your issue** The direct dependency here leads to some invalid version on an "npm ls" I'm not sure why its added as a direct dependency and not as a peerDependency.
What version of Tailwind CSS are you using? v4.3.1 What build tool (or framework if it abstracts the build tool) are you using? postcss@8.5.16 What version of Node.js are you using? v24.18.0 What browser are you using? Irrelevant What operating system are you using? Fedora 44, but issue occurs anywhere Reproduction Steps Describe your issue** Trying to use with latest version results in the following type error: This happens because pins postcss to v8.5.15, whose types are not forward compatible with v8.5.16. This can be worked around when using npm by forcing newer postcss to get installed: Possible solutions: bump pinned postcss dependency to 8.5.16 (may require future bumps for future versions) use a caret for version range, as postcss respects semver IMO caret is preferred, but this is at your discretion.
Repository: tailwindlabs/tailwindcss. Description: A utility-first CSS framework for rapid UI development. Stars: 95692, Forks: 5309. Primary language: TypeScript. Languages: TypeScript (81.8%), Rust (15.8%), JavaScript (0.8%), CSS (0.6%), HTML (0.6%). License: MIT. Homepage: https://tailwindcss.com/ Topics: css, css-framework, functional-css, postcss, responsive, tailwindcss, utility-classes. Latest release: v4.3.2 (1d ago). Open PRs: 26, open issues: 40. Last activity: 1d ago. Community health: 62%. Top contributors: adamwathan, RobinMalfait, depfu[bot], thecrypticace, dependabot-preview[bot], reinink, philipp-spiess, bradlc, dependabot-support, MichaelDeBoey and others.