@tailcloak/next
v0.4.0
Published
Obfuscate Tailwind CSS v4 class names in Next.js production builds. One line in next.config, Turbopack and webpack.
Maintainers
Readme
@tailcloak/next
Obfuscates Tailwind CSS v4 class names in Next.js production builds, with Turbopack or webpack. Each class string becomes one short, prefixed name.
Requires Next.js 15.3+, Tailwind CSS v4.1+ and Node.js 20.19+.
Setup
npm i -D @tailcloak/next
npx tailcloak initinit writes a tailcloak.config.ts with a random secret seed at your repository root. Commit it. Production builds fail without a seed.
// next.config.ts
import { withTailcloak } from "@tailcloak/next";
import type { NextConfig } from "next";
const nextConfig: NextConfig = {};
export default withTailcloak(nextConfig);Keep your stock postcss.config.mjs with @tailwindcss/postcss. next build obfuscates; next dev is left untouched.
Options
Set options in tailcloak.config.ts, or pass them as the second argument: withTailcloak(nextConfig, { prefix: "tc_" }).
See tailcloak for every option, what gets rewritten, and the limitations.
How it works
withTailcloak adds two loaders, for both Turbopack and webpack:
- Tailwind entry stylesheets (non-module
.cssfiles that importtailwindcss) are compiled by Tailwind and obfuscated before Next's PostCSS runs.@tailwindcss/postcssthen finds no Tailwind at-rules left, so nothing is compiled twice. - JS/TS/JSX modules outside
node_modulesget their class names renamed to match.
License
MIT
