Node.js-specific utilities and runtime functionality for Tailwind CSS v4, providing compilation tools, module dependency analysis, source map handling, path normalization, and optimization utilities.
Measure nested operations with hierarchical timers and hit counters, producing a readable tree report. Timing calls should form a parent/child structure that mirrors how work is nested, and counters should surface alongside their related timers. Repeated timers with the same label under a parent should merge into one node that accumulates duration and hits.
@generates
The profiler should:
root when none is provided.time or start/stop cycle as a hit on the corresponding node.ms.export interface TimerNode {
label: string;
durationMs: number;
hits: number;
children: TimerNode[];
}
export interface Profiler {
time<T>(label: string, fn: () => T | Promise<T>): T | Promise<T>;
start(label: string): () => void;
hit(label: string): void;
report(): { tree: TimerNode; text: string };
reset(): void;
dispose(): string;
}
export interface ProfilerOptions {
rootLabel?: string;
debugPattern?: string;
log?: (text: string) => void;
timeSource?: () => number;
}
export function createProfiler(options?: ProfilerOptions): Profiler;Provides hierarchical timing and hit-count instrumentation for building reports.
tessl i tessl/npm-tailwindcss--node@4.1.0docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10