@aaqu/fromcubes-tailwind 0.1.2

Fromcubes CSS engine: Tailwind CSS 4 generated server-side, with editor class completion as in Tailwind CSS IntelliSense

npm install @aaqu/fromcubes-tailwind

@aaqu/fromcubes-tailwind

Tailwind CSS 4 for @aaqu/fromcubes-react portals — a Node-RED plugin that registers the CSS engine tailwind.

• At deploy, each portal's source is scanned for class names and only the utilities it uses are built — server-side, no CDN, no browser compiler.
• In the editor, className="…" completes the way Tailwind CSS IntelliSense does in VS Code, from Tailwind's own design system: every class and variant, colour swatches, /50-style modifiers, and the generated CSS — with theme values and pixel sizes — beside each suggestion and on hover. Colour squares sit next to colour classes in the code (the picker rewrites arbitrary ones like bg-[#f00]), and the same warnings appear, with quick fixes: classes that set the same CSS (p-2 p-4) and classes with a canonical spelling (w-[16px] → w-4).

Install

cd ~/.node-red
npm install @aaqu/fromcubes-tailwind
# restart Node-RED

Requires @aaqu/fromcubes-react (a peer dependency — npm installs it if it is missing). Once installed, tailwind becomes the CSS engine by itself — there is nothing to set (unless you chose another engine before); Menu → Settings → Fromcubes shows it and lets you switch engines. Without this add-on the core serves portals with no generated stylesheet.

Limitations

Only complete class names in the source are seen: bg-${tone}-500 produces no CSS. Write the full names (tone === "red" ? "bg-red-500" : "bg-blue-500").

Support

fromcubes is built and maintained by one person. If it saves you time, consider sponsoring its development:

License

Apache-2.0