mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
ab82efab7d
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.
17 lines
627 B
TypeScript
17 lines
627 B
TypeScript
import * as Module from 'node:module'
|
|
import { pathToFileURL } from 'node:url'
|
|
import * as env from './env'
|
|
export * from './compile'
|
|
export * from './normalize-path'
|
|
export { env }
|
|
|
|
// In Bun, ESM modules will also populate `require.cache`, so the module hook is
|
|
// not necessary.
|
|
if (!process.versions.bun) {
|
|
// `Module#register` was added in Node v18.19.0 and v20.6.0
|
|
//
|
|
// Not calling it means that while ESM dependencies don't get reloaded, the
|
|
// actual included files will because they cache bust directly via `?id=…`
|
|
Module.register?.(pathToFileURL(require.resolve('@tailwindcss/node/esm-cache-loader')))
|
|
}
|