@sanmid/flux 0.1.5 → 0.1.7

package/README.md

@@ -44,26 +44,15 @@ Open your app at `http://localhost:3000` (or your dev URL). Toggle the editor wi
 
 ## Tailwind
 
-Include the built bundle in `content` so utilities used inside Flux are generated:
-
-```js
-// tailwind.config.ts
-export default {
-  content: [
-    "./app/**/*.{ts,tsx}",
-    "./components/**/*.{ts,tsx}",
-    "./node_modules/@sanmid/flux/dist/index.js",
-  ],
-};
-```
+Flux **injects its own utility CSS** for light-DOM UI (floating toggle, copy overlay, etc.), so you **do not** need to add Flux to your Tailwind `content` for normal use.
+
+If you fork Flux or build from source and change its class names, add your paths (or the published bundle) to `content` so your build picks up those utilities.
 
 ## Next.js
 
-```js
-const nextConfig = {
-  transpilePackages: ["@sanmid/flux"],
-};
-```
+**No extra Next config** — the published build ships **ESM and CJS** (`package.json` `exports`) and a **`"use client"`** banner so the App Router can consume `@sanmid/flux` like any other dependency. Mount `DesignEditor` from a client component (as in [Local development](#local-development-localhost)) and you are done.
+
+If you ever hit a resolution error on an older Next.js release, try adding `transpilePackages: ["@sanmid/flux"]` to `next.config` as a fallback.
 
 ## Security