tailwindcss

Fixes #20510 doesn't hide a `sr-only1pxclip-path: inset(50%)widthheight: 1pxoverflow: hiddenclip-pathclip-pathsr-onlyclip-pathsr-only:where(...)not-sr-onlysr-only md:not-sr-onlypackages/tailwindcss/src/utilities.test.tssr-only.sr-only > caption { clip-path: inset(50%) }packages/tailwindcss/tests/ui.spec.tsclip-pathinset(50%)sr-only md:not-sr-onlymdclip-pathnonedocument.elementFromPoint()inset(50%)inset(50%)--project=firefoxsandbox_extension_issue_file_to_process failed for …/plugin-container.app: 1 (Operation not permitted)browserType.launch` then times out), and no system Firefox is installed. So Firefox itself is the one engine I did not observe; the behaviour above comes from the issue report and the spec. The new test asserts the cascade rule rather than an engine-specific box layout, which is why I'd expect it to hold in Firefox too — it should be confirmed by CI.

Fixes #20426. Summary resolves CSS with a custom Vite resolver. That resolver spread the user's config but then overwrote with a hardcoded list (), so user-configured were silently dropped for CSS even though they were honoured for JS imports. This happened in both resolver branches (legacy pre-Environment-API and Environment API). The fix merges instead of overwrites: so the built-in conditions keep priority while user conditions still apply. Test plan Added regression tests in covering both resolver branches: vite (Environment API) and vite (legacy). A fixture package exposes under a export and under /; with the built CSS must contain the custom-condition rule. 2/2 new tests pass; full : 15/15 pass. Verified with the real Vite 8 resolver using the exact option shapes: old shape resolved (bug reproduced), new shape resolves (fixed). Prettier clean on both changed files; reports 0 errors in the changed file (remaining 39 errors elsewhere in the monorepo are pre-existing environmental issues unrelated to this change). Note: the fixture includes in the test CSS (with an explanatory comment) because the plugin returns early for files without Tailwind features, so the resolver under test would never run otherwise.

Problem When installing in an environment using strict (especially ), users experience and errors related to the WASM fallback runtime packages (, , , ). The issue stems from listing these packages in both and . Because of how workspaces (which this monorepo uses) handle symlinking, the actual are not fully packed into the published tarball for . When end-users install the package using , expects bundled dependencies to already exist inside the downloaded tarball and skips fetching them from the registry. Since they are missing from the tarball, surfaces unmet dependency errors and blocks strict installations. Solution This PR strips the array from . Since these packages are already correctly listed under standard , removing them from forces , , and to correctly fetch and resolve them from the registry during installation, completely eliminating the errors. Implementation details:** 1. Manually removed from . 2. Updated to automatically strip from the package.json during the lifecycle. This ensures that even if automatically injects during , they are stripped immediately before packing/publishing. Verification Locally verified that the in is correctly mutated post-build and no longer includes , while preserving all functional .