@csszyx/mcp-server 0.15.2 → 0.15.3

package/llms-full.txt

@@ -4087,9 +4087,13 @@ the built HTML carries no executable inline script and a strict CSP
 If an `sz`-generated utility also appears as a static string or template quasi in a
 source-level `class` or `className` attribute/property (including a `clsx(...)`
 expression), csszyx keeps that class unmangled. This ensures raw and `sz` consumers
-continue to reference the same emitted rule. Use `mangleExclude` when the class is
-only visible through an imported constant, DOM selector/class API, ignored
-dependency, downstream macro, or another value unavailable to the source scan.
+continue to reference the same emitted rule. When something else depends on the
+class NAME — a stylesheet matching by attribute (`[class*="bg-tag"]`), a DOM
+query, a class assembled outside any visible `className` — list it in
+`production.manglePreserve` (exact name, or a prefix ending in `*`); the
+hybrid-hazard warning prints a paste-ready value. `production.mangleExclude` is
+the other switch: it keeps the allocator from producing a token equal to a short
+class in third-party CSS, and never keeps a csszyx class from being renamed.
 
 Final-output class mangling is available in Vite, Webpack, and Rollup. The esbuild
 adapter keeps class names readable (and warns when `production.mangle: true` is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@csszyx/mcp-server",
-  "version": "0.15.2",
+  "version": "0.15.3",
   "description": "Model Context Protocol (MCP) server for csszyx — enables AI agents to understand and generate sz props",
   "license": "MIT",
   "type": "module",
@@ -28,9 +28,9 @@
     "node": "^22.18.0 || >=24.11.0"
   },
   "dependencies": {
-    "@csszyx/cli": "0.15.2",
-    "@csszyx/compiler": "0.15.2",
-    "@csszyx/unplugin": "0.15.2",
+    "@csszyx/cli": "0.15.3",
+    "@csszyx/compiler": "0.15.3",
+    "@csszyx/unplugin": "0.15.3",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^4.4.3"
   },