{"schema_version":1,"generated_by":"Master Diego","source":"github","region":"","language":"en","period_start":1780908214663,"period_end":1788684268808,"created_at":1788684268808,"targets":[{"external_id":"tailwindlabs/tailwindcss","name":"tailwindcss","owner":"tailwindlabs","url":"https://github.com/tailwindlabs/tailwindcss","is_own":false,"ref":"tailwindlabs/tailwindcss"}],"harvest":{"items_read":294,"items_new":294,"releases_seen":30,"window_days":90,"items_analysed":294},"sections":[{"target_external_id":"tailwindlabs/tailwindcss","target_name":"tailwindcss","is_own":false,"clusters":[{"label":"Why is the custom theme font sans variable not applied correctly?","slug":"why-is-the-custom-theme-font-sans-variable-not-applied-corre","distinct_people":5,"item_count":8,"first_asked":1781079507000,"last_asked":1785296521000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"This change should have been released by at least an minor level. It is too destructive to be included in a patch release. > GitHub …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20348#issuecomment-5112555331","created_at":1785296521000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"Well yes, I've easily set the fonts that used to be default manually. It is fixed for me. I just wished to inform you you …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20348#issuecomment-5033615022","created_at":1784634870000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"Same issue on my site. Here's the diff that my visual regression tests caught: ![\"Image\"](\"https://github.com/user-)
You could try using `--poll` as a work-around (#20297). Unreleased but available in `insiders` tag: Thanks for the suggestion! Tried it, but `--poll` doesn't …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20322#issuecomment-4952333869","created_at":1783881932000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> Alright, concretely, can you verify that a normal build (without --watch) is at least fast now? A normal build is fast, yes: With watchman, …","url":"https://github.com/tailwindlabs/tailwindcss/issues/15750#issuecomment-4843757373","created_at":1782824570000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"I'm having the same issue, is it really still Windows fault on `v4.3.1` with `-w always` on a PHP project inside Docker with a `run.js` …","url":"https://github.com/tailwindlabs/tailwindcss/issues/18118#issuecomment-4831316169","created_at":1782727899000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does npm ci fail due to missing packages in lock file?","slug":"why-does-npm-ci-fail-due-to-missing-packages-in-lock-file","distinct_people":2,"item_count":4,"first_asked":1783086689000,"last_asked":1783958774000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"I think I found the npm related reports: https://github.com/npm/cli/issues/9321 https://github.com/npm/cli/issues/4828 https://github.com/npm/cli/issues/ …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20324#issuecomment-4959998960","created_at":1783958774000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> @nilsbtr try using a normal `npm install` first such that your `package-lock.json` file is up to date. I tried that. I also tried multiple …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20016#issuecomment-4877612201","created_at":1783092013000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the @apply directive fail in less files after upgrade?","slug":"why-does-the-apply-directive-fail-in-less-files-after-upgrad","distinct_people":2,"item_count":2,"first_asked":1780985688000,"last_asked":1781749943000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Using @reference combined with @apply syntax within a style tag with lang=\"scss\" is invalid","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** **What version of …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20253","created_at":1781749943000,"rating":null,"release":null,"creator_replied":null},{"title":"`@apply` No Longer Works in `.less` Files After Upgrading to Tailwind CSS v4","snippet":"After upgrading from Tailwind CSS v3 to v4, all `@apply` directives inside `.less` files are broken. The build fails and styles are not applied. - …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20209","created_at":1780985688000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does TypeScript export syntax conflict with Deno check?","slug":"why-does-typescript-export-syntax-conflict-with-deno-check","distinct_people":2,"item_count":2,"first_asked":1781209633000,"last_asked":1781350694000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"@tailwindcss/vite 4.3.1 breaks Vite tsconfig extends resolution under Deno","snippet":"tailwindcss/vite@4.3.1` breaks Vite's tsconfig `extends` resolution when running under Deno with `nodeModulesDir: \"auto\"` and npm imports from `deno.json`. The same reproducti …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20232","created_at":1781350694000,"rating":null,"release":null,"creator_replied":null},{"title":"types: export = in @tailwindcss/postcss contradicts exports.import in package.json","snippet":"TypeScript 6.0 (shipped in Deno v2.8.3) changed `export =` in ESM context from a warning (TS1203) to a hard error (TS1192). This causes `deno check` …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20219","created_at":1781209633000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why do gradients vanish silently on older Chrome browsers?","slug":"why-do-gradients-vanish-silently-on-older-chrome-browsers","distinct_people":2,"item_count":2,"first_asked":1781213273000,"last_asked":1785491713000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Filter utilities not working in old chromium versions","snippet":"What version of Tailwind CSS are you using?** **What browser are you using?** Chrome/Chromium (v112 & v150) https://play.tailwindcss.com/u7h2BGRLEb **Describe your issue** For …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20371","created_at":1785491713000,"rating":null,"release":null,"creator_replied":null},{"title":"Default gradient interpolation (`in oklab`) has no fallback — gradients silently vanish on Chrome ≤110 (IACVT via `syntax:\"*\"` custom property)","snippet":"What version of Tailwind CSS are you using?** v4.3.0 (latest), via `@tailwindcss/postcss` under Next.js 16 / Turbopack. **Describe your issue** The **default** gradient interp …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20220","created_at":1781213273000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why is the group hover selector broken by postcss-selector-parser update?","slug":"why-is-the-group-hover-selector-broken-by-postcss-selector-p","distinct_people":2,"item_count":2,"first_asked":1781229279000,"last_asked":1781779129000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Resolves text-[--spacing(n)] as color instead of font-size","snippet":"What version of Tailwind CSS are you using?** For example: v4.3.0, v4.3.1 **What build tool (or framework if it abstracts the build tool) are you …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20256","created_at":1781779129000,"rating":null,"release":null,"creator_replied":null},{"title":"postcss-selector-parser version update cause bug","snippet":"https://github.com/tailwindlabs/tailwindcss/blob/b01283cc9b66cf830d87cbfe1fbb5ebb8561226a/src/util/formatVariantSelector.js#L252 postcss-selector-parser from 6.1.2 to 6.1.3 , …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20222","created_at":1781229279000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the CLI crash when using the @source directive?","slug":"why-does-the-cli-crash-when-using-the-source-directive","distinct_people":2,"item_count":2,"first_asked":1781334003000,"last_asked":1781774881000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Tailwind CSS 4.3.1 hangs in source scanner with @source \"../../app.config.ts\" used by Docus","snippet":"I'm seeing a startup/build hang when using the latest Docus project with Tailwind CSS 4.3.1. The issue occurs on a fresh project generated by …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20255","created_at":1781774881000,"rating":null,"release":null,"creator_replied":null},{"title":"v4.3.1 CLI fails with [Error: Invalid handle] when @source present","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** tailwindcss -i ./css/ …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20231","created_at":1781334003000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the standalone CLI crash on macOS 27 with code 9?","slug":"why-does-the-standalone-cli-crash-on-macos-27-with-code-9","distinct_people":2,"item_count":2,"first_asked":1781548299000,"last_asked":1786359620000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Tailwind-Cli not signed for MacOS and therefor fails with the error \"Tailwind-Cli is damaged and can't be opened. You should move it to …","snippet":"Issue Description** MacOS gotten over the years much more uptight on signing requirements for binaries and currently the MacOS client can't be executed frequently failing …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20404","created_at":1786359620000,"rating":null,"release":null,"creator_replied":null},{"title":"Tailwind cli fails on macOS 27 with code 9","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** The standalone CLI, …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20243","created_at":1781548299000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does text-[--spacing(n)] resolve as color instead of font-size?","slug":"why-does-text-spacing-n-resolve-as-color-instead-of-font-siz","distinct_people":2,"item_count":2,"first_asked":1783606739000,"last_asked":1786047886000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"So... took a look at the PR for this #19773 since it's been open since March without review and has gone stale yet is still …","url":"https://github.com/tailwindlabs/tailwindcss/issues/19722#issuecomment-5208892050","created_at":1786047886000,"rating":null,"release":null,"creator_replied":null},{"title":"--spacing(0) now resolves to a unitless 0, breaking downstream calc()","snippet":"related https://github.com/cosscom/coss/issues/803 From 4.3.1 onward, --spacing(0) (and *-0 spacing utilities) compile to a bare unitless 0 instead of calc( …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20315","created_at":1783606739000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the WASM fallback fail on HarmonyOS due to sandbox permission restrictions?","slug":"why-does-the-wasm-fallback-fail-on-harmonyos-due-to-sandbox","distinct_people":2,"item_count":2,"first_asked":1783836165000,"last_asked":1783957848000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"Yes, running `npm install` was one of the first things we tried. This may ultimately be an npm issue rather than a Tailwind issue, but …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20324#issuecomment-4959852743","created_at":1783957848000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"@RobinMalfait Fair questions — I went and actually measured this instead of just asserting \"slower\". Here's what I found on a real HarmonyOS device (HongMeng …","url":"https://github.com/tailwindlabs/tailwindcss/pull/20276#issuecomment-4950167198","created_at":1783836165000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does hot reload fail for symlinks behind workspaces?","slug":"why-does-hot-reload-fail-for-symlinks-behind-workspaces","distinct_people":2,"item_count":2,"first_asked":1784274868000,"last_asked":1784327080000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"Testing this a bit further, the same class shows up in the scanner's other consumers. The CLI's native `--watch` is affected with the mechanism inverted: …","url":"https://github.com/tailwindlabs/tailwindcss/pull/20347#issuecomment-5008055957","created_at":1784327080000,"rating":null,"release":null,"creator_replied":null},{"title":"@tailwindcss/vite does not hot-reload new candidates from explicit @source files behind workspace symlinks since v4.3.1","snippet":"What version of Tailwind CSS are you using?** This regressed between v4.3.0 and v4.3.1 and is still reproducible in v4.3.3. **What build tool (or framework …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20346","created_at":1784274868000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why is the :is selector generation incorrect for BEM modifier nesting?","slug":"why-is-the-is-selector-generation-incorrect-for-bem-modifier","distinct_people":2,"item_count":2,"first_asked":1785220806000,"last_asked":1785235638000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"@RobinMalfait I know that. We run other postcss plugins to ensure browser compatibility etc. Does this seem correct? I would expect it to make the …","url":"https://github.com/tailwindlabs/tailwindcss/pull/20124#issuecomment-5103140044","created_at":1785235638000,"rating":null,"release":null,"creator_replied":null},{"title":"v4.3.3: &--modifier &__element nesting produces invalid :is() selectors","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** @tailwindcss/postcss via …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20358","created_at":1785220806000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does PHPStorm flag valid dark mode utility classes as redundant?","slug":"why-does-phpstorm-flag-valid-dark-mode-utility-classes-as-re","distinct_people":2,"item_count":2,"first_asked":1785308406000,"last_asked":1785385553000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"PhpStorm flags valid dark: utility classes as redundant","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** **What version of …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20363","created_at":1785385553000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> What OS are you on where you see the issue? Plus, what is the system language of your OS (especially if you are using …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20348#issuecomment-5114263052","created_at":1785308406000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the scanner emit invalid UTF-8 sequences from source?","slug":"why-does-the-scanner-emit-invalid-utf-8-sequences-from-sourc","distinct_people":2,"item_count":2,"first_asked":1785443165000,"last_asked":1785630668000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"So I reproduced this without the race and it looks like a soundness bug potentially. A .tsx file with one stray continuation byte in a …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20368#issuecomment-5154195265","created_at":1785630668000,"rating":null,"release":null,"creator_replied":null},{"title":"Scanned candidate emitted with corrupted bytes (`child` → `U+FFFD \\x06 U+FFFD \\x01`) by a long-lived `next dev` (Turbopack) process — evidence against the scanner's ` …","snippet":"A long-running `next dev` (Turbopack) process in a pnpm monorepo entered a state where Tailwind's generated CSS contained a corrupted copy of one arbitrary- …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20368","created_at":1785443165000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why is the specific release version containing the fix not identified?","slug":"why-is-the-specific-release-version-containing-the-fix-not-i","distinct_people":2,"item_count":2,"first_asked":1782800943000,"last_asked":1785070158000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"Since 4.3.2 fixes this, the actionable part is probably identifying which change fixed it and whether it warrants a 4.1.x backport — the report is …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20354#issuecomment-5083540861","created_at":1785070158000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> Beautiful! Yep everything that goes into the main branch is released in the insiders build and eventually makes it into a release (if we …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20016#issuecomment-4840526538","created_at":1782800943000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why are class names adjacent to brackets not extracted?","slug":"why-are-class-names-adjacent-to-brackets-not-extracted","distinct_people":1,"item_count":2,"first_asked":1781384305000,"last_asked":1781388858000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Class names adjacent to [ and ] delimiters not extracted","snippet":"tailwind-tt-repro.zip](https://github.com/user-attachments/files/28919537/tailwind-tt-repro.zip) **What version of Tailwind CSS are you using?** **What build tool (or framewor …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20233","created_at":1781388858000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why is the source path incorrectly resolved to /users folder?","slug":"why-is-the-source-path-incorrectly-resolved-to-users-folder","distinct_people":1,"item_count":1,"first_asked":1781778605000,"last_asked":1781778605000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"@RobinMalfait No, there is no /Users/app.config.ts file on my machine. My project is located at: `/Users/fachrihilmi/docus-test` and there is no app.config.ts …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20255#issuecomment-4741042987","created_at":1781778605000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does group-hover not work on mobile devices?","slug":"why-does-group-hover-not-work-on-mobile-devices","distinct_people":1,"item_count":1,"first_asked":1782231034000,"last_asked":1782231034000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"group-hover not working on mobile","snippet":"opacity-0 group-hover:opacity-100 remains hidden on mobile view, I have content hover on image - on desktop, group-hover working fine, but when i …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20271","created_at":1782231034000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why are variant classes not generated when using prefix?","slug":"why-are-variant-classes-not-generated-when-using-prefix","distinct_people":1,"item_count":1,"first_asked":1782716126000,"last_asked":1782716126000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"[v4] Variant classes (hover:, disabled:, etc.) are not generated when using prefix() - Breaking for any project using CSS prefix isolation","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** @tailwindcss/vite 4.3.1, …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20284","created_at":1782716126000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the compiler cache ignore changed input CSS when mtime is unchanged?","slug":"why-does-the-compiler-cache-ignore-changed-input-css-when-mt","distinct_people":1,"item_count":1,"first_asked":1783208448000,"last_asked":1783208448000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"`@tailwindcss/postcss`: compiler cache ignores changed input CSS when `from`'s mtime is unchanged — stale output with any preprocessor (Sass) pipeline","snippet":"Tailwind version:** 4.3.2 (`tailwindcss` + `@tailwindcss/postcss`, latest at time of filing) **Node:** 22.x · reproduces on macOS and Linux `@tailwindcss/postcss` keeps a per- …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20307","created_at":1783208448000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the CLI crash on Android Termux due to missing native build fallback?","slug":"why-does-the-cli-crash-on-android-termux-due-to-missing-nati","distinct_people":1,"item_count":1,"first_asked":1783810866000,"last_asked":1783810866000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Tailwind v4 CLI crashes on Android/Termux due to missing native build fallback (`@parcel/watcher`)","snippet":"When running the Tailwind v4 CLI (@tailwindcss/cli@4.3.2) inside a **Termux (Android)** environment using Node.js v24, the CLI crashes instantly during tw:dev (watch mode). …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20322","created_at":1783810866000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the upgrade tool rewrite node_modules files?","slug":"why-does-the-upgrade-tool-rewrite-node-modules-files","distinct_people":1,"item_count":1,"first_asked":1784041980000,"last_asked":1784041980000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"`@tailwindcss/upgrade` rewrites files in `node_modules` when run from a pnpm workspace subpackage","snippet":"When `@tailwindcss/upgrade` is run from a **subpackage of a pnpm workspace**, it traverses `../../node_modules/…` and rewrites files inside the installed `tailwindcss` package …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20328","created_at":1784041980000,"rating":null,"release":null,"creator_replied":null}]},{"label":"Why does the root source hide nested sources regression?","slug":"why-does-the-root-source-hide-nested-sources-regression","distinct_people":1,"item_count":1,"first_asked":1784107524000,"last_asked":1784107524000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Root-level concrete @source hides nested concrete sources with source(none) in v4.3.2","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** Vite 8.1.4 with …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20333","created_at":1784107524000,"rating":null,"release":null,"creator_replied":null}]}],"not_established":null}],"new_this_week":[{"label":"Why is the custom theme font sans variable not applied correctly?","slug":"why-is-the-custom-theme-font-sans-variable-not-applied-corre","distinct_people":5,"item_count":8,"first_asked":1781079507000,"last_asked":1785296521000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"This change should have been released by at least an minor level. It is too destructive to be included in a patch release. > GitHub …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20348#issuecomment-5112555331","created_at":1785296521000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"Well yes, I've easily set the fonts that used to be default manually. It is fixed for me. I just wished to inform you you …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20348#issuecomment-5033615022","created_at":1784634870000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"Same issue on my site. Here's the diff that my visual regression tests caught: You could try using `--poll` as a work-around (#20297). Unreleased but available in `insiders` tag: Thanks for the suggestion! Tried it, but `--poll` doesn't …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20322#issuecomment-4952333869","created_at":1783881932000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> Alright, concretely, can you verify that a normal build (without --watch) is at least fast now? A normal build is fast, yes: With watchman, …","url":"https://github.com/tailwindlabs/tailwindcss/issues/15750#issuecomment-4843757373","created_at":1782824570000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"I'm having the same issue, is it really still Windows fault on `v4.3.1` with `-w always` on a PHP project inside Docker with a `run.js` …","url":"https://github.com/tailwindlabs/tailwindcss/issues/18118#issuecomment-4831316169","created_at":1782727899000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why does npm ci fail due to missing packages in lock file?","slug":"why-does-npm-ci-fail-due-to-missing-packages-in-lock-file","distinct_people":2,"item_count":4,"first_asked":1783086689000,"last_asked":1783958774000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"","snippet":"I think I found the npm related reports: https://github.com/npm/cli/issues/9321 https://github.com/npm/cli/issues/4828 https://github.com/npm/cli/issues/ …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20324#issuecomment-4959998960","created_at":1783958774000,"rating":null,"release":null,"creator_replied":null},{"title":"","snippet":"> @nilsbtr try using a normal `npm install` first such that your `package-lock.json` file is up to date. I tried that. I also tried multiple …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20016#issuecomment-4877612201","created_at":1783092013000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why does the @apply directive fail in less files after upgrade?","slug":"why-does-the-apply-directive-fail-in-less-files-after-upgrad","distinct_people":2,"item_count":2,"first_asked":1780985688000,"last_asked":1781749943000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Using @reference combined with @apply syntax within a style tag with lang=\"scss\" is invalid","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** **What version of …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20253","created_at":1781749943000,"rating":null,"release":null,"creator_replied":null},{"title":"`@apply` No Longer Works in `.less` Files After Upgrading to Tailwind CSS v4","snippet":"After upgrading from Tailwind CSS v3 to v4, all `@apply` directives inside `.less` files are broken. The build fails and styles are not applied. - …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20209","created_at":1780985688000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why does TypeScript export syntax conflict with Deno check?","slug":"why-does-typescript-export-syntax-conflict-with-deno-check","distinct_people":2,"item_count":2,"first_asked":1781209633000,"last_asked":1781350694000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"@tailwindcss/vite 4.3.1 breaks Vite tsconfig extends resolution under Deno","snippet":"tailwindcss/vite@4.3.1` breaks Vite's tsconfig `extends` resolution when running under Deno with `nodeModulesDir: \"auto\"` and npm imports from `deno.json`. The same reproducti …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20232","created_at":1781350694000,"rating":null,"release":null,"creator_replied":null},{"title":"types: export = in @tailwindcss/postcss contradicts exports.import in package.json","snippet":"TypeScript 6.0 (shipped in Deno v2.8.3) changed `export =` in ESM context from a warning (TS1203) to a hard error (TS1192). This causes `deno check` …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20219","created_at":1781209633000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why do gradients vanish silently on older Chrome browsers?","slug":"why-do-gradients-vanish-silently-on-older-chrome-browsers","distinct_people":2,"item_count":2,"first_asked":1781213273000,"last_asked":1785491713000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Filter utilities not working in old chromium versions","snippet":"What version of Tailwind CSS are you using?** **What browser are you using?** Chrome/Chromium (v112 & v150) https://play.tailwindcss.com/u7h2BGRLEb **Describe your issue** For …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20371","created_at":1785491713000,"rating":null,"release":null,"creator_replied":null},{"title":"Default gradient interpolation (`in oklab`) has no fallback — gradients silently vanish on Chrome ≤110 (IACVT via `syntax:\"*\"` custom property)","snippet":"What version of Tailwind CSS are you using?** v4.3.0 (latest), via `@tailwindcss/postcss` under Next.js 16 / Turbopack. **Describe your issue** The **default** gradient interp …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20220","created_at":1781213273000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why is the group hover selector broken by postcss-selector-parser update?","slug":"why-is-the-group-hover-selector-broken-by-postcss-selector-p","distinct_people":2,"item_count":2,"first_asked":1781229279000,"last_asked":1781779129000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Resolves text-[--spacing(n)] as color instead of font-size","snippet":"What version of Tailwind CSS are you using?** For example: v4.3.0, v4.3.1 **What build tool (or framework if it abstracts the build tool) are you …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20256","created_at":1781779129000,"rating":null,"release":null,"creator_replied":null},{"title":"postcss-selector-parser version update cause bug","snippet":"https://github.com/tailwindlabs/tailwindcss/blob/b01283cc9b66cf830d87cbfe1fbb5ebb8561226a/src/util/formatVariantSelector.js#L252 postcss-selector-parser from 6.1.2 to 6.1.3 , …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20222","created_at":1781229279000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why does the CLI crash when using the @source directive?","slug":"why-does-the-cli-crash-when-using-the-source-directive","distinct_people":2,"item_count":2,"first_asked":1781334003000,"last_asked":1781774881000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Tailwind CSS 4.3.1 hangs in source scanner with @source \"../../app.config.ts\" used by Docus","snippet":"I'm seeing a startup/build hang when using the latest Docus project with Tailwind CSS 4.3.1. The issue occurs on a fresh project generated by …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20255","created_at":1781774881000,"rating":null,"release":null,"creator_replied":null},{"title":"v4.3.1 CLI fails with [Error: Invalid handle] when @source present","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** tailwindcss -i ./css/ …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20231","created_at":1781334003000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"},{"label":"Why does the standalone CLI crash on macOS 27 with code 9?","slug":"why-does-the-standalone-cli-crash-on-macos-27-with-code-9","distinct_people":2,"item_count":2,"first_asked":1781548299000,"last_asked":1786359620000,"is_new":true,"previous_people":null,"release_spike":null,"evidence":[{"title":"Tailwind-Cli not signed for MacOS and therefor fails with the error \"Tailwind-Cli is damaged and can't be opened. You should move it to …","snippet":"Issue Description** MacOS gotten over the years much more uptight on signing requirements for binaries and currently the MacOS client can't be executed frequently failing …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20404","created_at":1786359620000,"rating":null,"release":null,"creator_replied":null},{"title":"Tailwind cli fails on macOS 27 with code 9","snippet":"What version of Tailwind CSS are you using?** **What build tool (or framework if it abstracts the build tool) are you using?** The standalone CLI, …","url":"https://github.com/tailwindlabs/tailwindcss/issues/20243","created_at":1781548299000,"rating":null,"release":null,"creator_replied":null}],"target_name":"tailwindcss"}],"base_rate_note":"Threads are counted per distinct account. Bots and pull requests are excluded.","method_note":"Source: GitHub. 294 threads analysed over 90 days. 63 posts by the project's own maintainers are excluded from every count.","method_facts":{"items_new":294,"items_read":294,"items_analysed":294,"staff_excluded":63},"since_last":{"has_previous":false,"new":25,"rising":0,"falling":0,"gone":0,"gone_labels":[]}}