PB_TAILWIND_CLASS_MISSING

What happened

A Tailwind class was used in the HTML but was not detected by Paperbase's JIT compiler. The class has no effect on the output.

How to fix

This usually happens with dynamically constructed class names (e.g., `text-${color}-500`). Paperbase's JIT scans the static HTML, so dynamic classes need to be written out statically.

// Before — dynamic class (JIT can't detect "text-red-500")
`<div class="text-${color}-500">text</div>`
 
// After — static conditional
color === "red" ? "text-red-500" : "text-blue-500"

Why this happens

Tailwind's JIT mode works by scanning source files for class names as static strings. When a class name is assembled at runtime (string interpolation, array joins, etc.), the scanner misses it. The safest fix is to always use complete, static class name strings.