tailwindcss

What version of Tailwind CSS are you using? v4.1.18 What build tool (or framework if it abstracts the build tool) are you using? Vite 7.x (Next.js 16.x) What version of Node.js are you using? v22.x What browser are you using? N/A (build output issue) What operating system are you using? macOS Reproduction URL https://play.tailwindcss.com/8zse4OUjaq Describe your issue When defining a custom named spacing value in , the utility outputs instead of the expected . Reproduction CSS: Expected: outputs (as documented and as the fallback intends). Actual: outputs , sourced from . Root cause in source: The utility is defined with theme keys . When resolving : 1. is not defined in the default theme 2. is found via the fallback namespace 3. The () is never reached because the theme lookup succeeded first This means any custom named value that shares a suffix with a static value will shadow it. The fallback is needed for numeric values like → , but named values create unintended collisions. Workaround: Explicitly define in to take priority over the fallback. Note: The theme documentation describes as affecting "spacing and sizing utilities like , " — line-height is not mentioned as affected. This behavior contradicts that documentation.

What version of Tailwind CSS are you using? v4.2.1 What build tool (or framework if it abstracts the build tool) are you using? tailwindcss-windows-x64.exe What version of Node.js are you using? N/A What browser are you using? Edge What operating system are you using? Windows ARM64 in Parallels MacOS M4-Max Reproduction URL N/A Describe your issue** Since there is no logging that I can see, I can't see how to duplicate it. At first, tailwindcss-windows-x64.exe worked flawlessly, but as my project grew, the --watch may fully build the project, but exit shortly later, or it exits several times without building. My workaround has been using terminal in MacOS to a network share of my project. It builds flawlessly, but the --watch doesn't see changes over the network, so I just have to run the command every time I make a change. I would expect that an arm64 build of tailwindcss-windows-arm64.exe would solve the problem.

Summary This PR updates the contributing guide to use pnpm’s script shorthand for consistency and copy/paste friendliness: → → These commands are equivalent, but the shorthand matches the rest of the repo’s script usage and reduces noise in documentation. Test plan Verified the and scripts exist in the root . Ran Prettier formatting check on the edited file: ```sh pnpm prettier --check .github/CONTRIBUTING.md