Robin Malfait ab82efab7d Expose timing information in debug mode (#14553) ... This PR exposes when using the the `DEBUG` environment variable. This follows the `DEBUG` conventions where: - `DEBUG=1` - `DEBUG=true` - `DEBUG=*` - `DEBUG=tailwindcss` Will enable the debug information, but when using: - `DEBUG=0` - `DEBUG=false` - `DEBUG=-tailwindcss` It will not. This currently only exposes some timings related to: 1. Scanning for candidates 2. Building the CSS 3. Optimizing the CSS We can implement a more advanced version of this where we also expose more fine grained information such as the files we scanned, the amount of candidates we found and so on. But I believe that this will be enough to start triaging performance related issues.		2024-09-30 14:39:21 +00:00
..
@tailwindcss-cli	Expose timing information in debug mode (#14553)	2024-09-30 14:39:21 +00:00
@tailwindcss-node	Expose timing information in debug mode (#14553)	2024-09-30 14:39:21 +00:00
@tailwindcss-postcss	Expose timing information in debug mode (#14553)	2024-09-30 14:39:21 +00:00
@tailwindcss-standalone	Update @types/bun 1.1.8 → 1.1.10 (patch) (#14542)	2024-09-28 11:20:51 +00:00
@tailwindcss-upgrade	CSS codemod: inject @import in a more expected location (#14536)	2024-09-30 13:32:30 +00:00
@tailwindcss-vite	Expose timing information in debug mode (#14553)	2024-09-30 14:39:21 +00:00
internal-example-plugin	Prefix internal modules with internal-* (#14074)	2024-07-29 10:58:07 -04:00
tailwindcss	Remove process.env.VERSION check (#14531)	2024-09-27 05:29:40 -04:00
tsconfig.base.json	introduce v4 codebase	2024-03-05 14:29:15 +01:00