@csszyx/mcp-server 0.13.0 → 0.14.1

package/dist/index.mjs

@@ -6,7 +6,7 @@ import { fileURLToPath } from 'node:url';
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { ListToolsRequestSchema, CallToolRequestSchema, ListResourcesRequestSchema, ReadResourceRequestSchema, ListPromptsRequestSchema, GetPromptRequestSchema } from '@modelcontextprotocol/sdk/types.js';
-import { sortStrings, SPECIAL_VARIANTS, KNOWN_VARIANTS, PROPERTY_MAP, transform, transformSourceCode, SUGGESTION_MAP, BOOLEAN_SHORTHANDS, REMOVED_BOOLEAN_SUGAR } from '@csszyx/compiler';
+import { sortStrings, SPECIAL_VARIANTS, KNOWN_VARIANTS, PROPERTY_MAP, transform, transformSource, SUGGESTION_MAP, BOOLEAN_SHORTHANDS, REMOVED_BOOLEAN_SUGAR, KNOWN_SPECIAL_PROPERTIES } from '@csszyx/compiler';
 import { z } from 'zod';
 import { migrateSource, classNameToSzObject } from '@csszyx/cli';
 import { parseThemeBlocks, hasTokens } from '@csszyx/unplugin';
@@ -350,7 +350,8 @@ const RUNTIME_HELPERS = [
   ["__szvPick1", "usesSzvPick1"],
   ["__szColorVar", "usesColorVar"],
   ["__szSpacingVar", "usesSpacingVar"],
-  ["__szUnitVar", "usesUnitVar"]
+  ["__szUnitVar", "usesUnitVar"],
+  ["__szBoolClass", "usesBoolClass"]
 ];
 function restoreEnv(name, value) {
   if (value === void 0) {
@@ -370,7 +371,7 @@ function compileWithDiagnostics(source, filename) {
   process.env.NODE_ENV = "development";
   delete process.env.CSSZYX_QUIET_SZ_WARNINGS;
   try {
-    return { result: transformSourceCode(source, filename), warnings };
+    return { result: transformSource(source, filename), warnings };
   } finally {
     console.warn = originalWarn;
     restoreEnv("NODE_ENV", originalNodeEnv);
@@ -668,8 +669,8 @@ function validateEntry(key, value) {
       suggestion: `Use { ${removed.key}: ${JSON.stringify(removed.value)} } instead.`
     };
   }
-  const isSpecial = ["css", "@container", "*"].includes(key) || key.startsWith("@") || key.startsWith("[");
-  const isKnown = key in PROPERTY_MAP || BOOLEAN_SHORTHANDS.has(key) || KNOWN_VARIANTS.has(key) || isSpecial;
+  const isSpecial = ["@container", "*"].includes(key) || key.startsWith("@") || key.startsWith("[");
+  const isKnown = key in PROPERTY_MAP || BOOLEAN_SHORTHANDS.has(key) || KNOWN_SPECIAL_PROPERTIES.has(key) || KNOWN_VARIANTS.has(key) || isSpecial;
   return isKnown ? void 0 : {
     key,
     message: `Unknown prop '${key}'. Not a valid sz key, variant, or special prop.`

package/llms-full.txt

@@ -244,6 +244,12 @@ sz={{ '@container': true, '@md': { display: 'flex' } }}
 { p: 4, bg: 'blue-500', display: 'flex', flexDir: 'col', w: '333px', mt: 4, text: 'lg' }
 ```
 
+Known CSS-name aliases and removed migration keys are rejected rather than
+auto-mapped: the compiler warns and emits no class. Rename the source to the
+canonical key or replacement shape. A truly unknown key is different: it warns
+but still emits a kebab-case candidate so an intentional Tailwind `@utility`
+can serve it.
+
 ## Type safety — unknown keys are TypeScript errors
 
 The `sz` prop type is **closed**: a key that is not a known sz prop or variant is a
@@ -1257,7 +1263,9 @@ moved into their layer (`{ maskLinear: { from } }` etc.), `maskShape` moved to
 `{ maskRadial: { shape } }`, `maskVia` was removed with no equivalent (Tailwind
 has no via stop for masks), and gradient layer values on `mask`
 (`{ mask: 'linear-45' }`) moved to the layer keys. `mask` carries only a direct
-mask-image: `none`, `url(…)`, a CSS variable, or an arbitrary value.
+mask-image: `none`, `url(…)`, a CSS variable, or an arbitrary value. The
+compiler warns and emits no class for every removed flat key; it never preserves
+them as custom-utility fallbacks.
 
 ### mask-image: Gradient Masks
 
@@ -3069,11 +3077,20 @@ needs "Use Workspace Version".
 - Insert numeric suggestions without quotes and string suggestions with quotes. Suggestions are not validation: Tailwind 4 numeric values are open-ended.
 - Preserve TypeScript's base completions. On cancellation, timeout, or internal failure, return the untouched base result.
 
-Defaults: `enabled: true`, `values: true`, `maxEntries: 512`,
-`deadlineMs: 20`, `failureThreshold: 3`. Usually emit only `{ "name":
+Defaults: `enabled: true`, `values: true`, `themeValues: false`,
+`maxEntries: 512`, `deadlineMs: 20`, `failureThreshold: 3`. Usually emit only `{ "name":
 "@csszyx/ts-plugin" }`; do not add tuning options without a demonstrated need.
 
-**Not provided by this plugin:** theme-aware values, hover previews,
+**Theme preview:** `themeValues: true` adds custom colors, spacings, fonts,
+text sizes, font weights, radii, shadows, and breakpoint keys from the leaf
+project's generated `.csszyx/theme.d.ts`. The declaration must already belong
+to the TypeScript Program. Parsing is AST-based and bounded (128 KiB source,
+2,000 tokens, 128 characters per token); missing/malformed input fails open.
+The plugin performs no CSS/filesystem scan, direct I/O, watcher, network, or
+Tailwind/config execution. VS Code extension users set
+`csszyx.themeValues: true`; the default remains off during host certification.
+
+**Not provided by this plugin:** hover previews,
 diagnostics, syntax highlighting, Tailwind config/plugin execution, network, or
 telemetry. Those capabilities must not be inferred. The plugin is
 self-contained: its metadata is bundled at build time, so it installs with no
@@ -3111,7 +3128,9 @@ IntelliSense, hover, and diagnostics for `sz` props. Supports JSX, TSX, JS, TS,
 
 - Key + value completions inside `sz={{ ... }}` (variant-aware, depth 1 and 2)
 - Hover preview — shows generated Tailwind className + inline CSS variables via `transform()`
-- Diagnostics — unknown prop keys flagged as warnings; SUGGESTION_MAP hints (e.g. `padding` → `p`)
+- Diagnostics — unknown prop keys flagged as warnings; removed aliases receive
+  canonical migration hints (for example `padding` → `p`) and emit no class,
+  while intentional custom keys remain available to Tailwind `@utility`
 - TextMate grammar injection — syntax highlighting for `sz` attribute
 
 **Settings:**
@@ -3659,6 +3678,7 @@ sz={{ scale: shrunk ? 75 : 100 }}            // inline prop ternary — both lit
 - `build.importedStaticSz` (default TRUE) compiles a static sz object imported from another module — v1 covers a direct `sz={binding}` from a NAMED import of an `export const` object literal, written relative or through a project alias (read from the bundler's `resolve.alias` and tsconfig `compilerOptions.paths`); barrels, package specifiers, absolute specifiers, namespace/default imports and nested positions keep the runtime fallback and report it; every lane defaults to on so nothing needs wiring, and turning it OFF must be done in all of them — `csszyxTurbopack({}, { importedStaticSz: false })` PLUS `csszyx next prebuild --no-imported-static-sz` PLUS `csszyx next watch --no-imported-static-sz` for dev — because a mismatch fails the production build on the config hash
 - A shared sz object is a build-time value: the compiler reads it where it is DECLARED. Reassigning the binding (`let s = {...}; s = {...}`) is detected and falls back to the runtime; a property write (`s.p = 8`) is NOT detected and the class still describes the declared value. Declare once, never write to it — vary with spread overrides or `szv()`
 - `sz={{ key: cond ? a : b }}` — both literal branches compile to static classes; a runtime branch uses a CSS variable. An opposite `undefined`, `null`, `false`, or `''` branch omits the utility and variable value (`0` remains valid)
+- Keys whose value is a boolean — `border` and every side, `ring`, `outline`, `shadow`, `truncate` — never use a CSS variable: a runtime value on them compiles to `__szBoolClass(value, key, "border-b")`, which renders the bare class for `true`, nothing for `false`/`null`/`undefined`/`''`, and warns for any other type instead of emitting a utility that would style a different property. React discards booleans in `style`, so the variable form could never have applied
 - When runtime `sz` values emit inline CSS variables beside one direct object-literal JSX spread, or one conditional whose branches are object literals, the compiler injects the variables into every spread branch's `style` so both authored and generated values survive. Keep unresolved or multiple spreads' style explicit; csszyx warns when it cannot prove a single-evaluation merge is safe
 - `sz={{ ...(cond ? a : b), static: val }}` — conditional spread hoist: compiler resolves both branches at build time
 - Imported variables / function call results fall back to `_sz()` runtime — a build-time compiler warning explains the fallback reason and suggests `szv()` or `dynamic()`. An expression rooted in an IMPORT collects no classes at all, so that warning is kept in production builds and survives `quiet: 'nudges'`; every other unresolved shape — including a forwarded `sz` prop, whose classes the caller contributes — stays dev-only advice
@@ -3905,15 +3925,17 @@ csszyx has two worlds; pick by "is the value set finite and known at build time?
 - **Runtime (`dynamic()`):** unbounded values (CMS color, user `#hex`). CSS is
   generated + injected in the browser via insertRule. Escape hatch only.
 
-Engines (BUILD-TIME parse of JSX source only): Rust native (default) → oxc (JS
-fallback) → babel (last resort). All three emit IDENTICAL classes (parity-gated) —
-engine only affects build speed, never output. The native binary ships as
-per-platform optional deps (`@csszyx/core-*`); if it's missing (unsupported arch,
-omitted optional deps, cross-platform frozen lockfile) the DEFAULT `rust` auto-
-degrades to `oxc` with a one-time warning — builds still succeed with identical
-classes. An EXPLICIT `parser:'rust'` (config or `CSSZYX_PARSER=rust`) hard-fails
-instead. Don't tell users a missing native binary breaks csszyx or changes
-classes; tell them to ignore the warning or set `build.parser:'oxc'`. The RUNTIME
+Engine (BUILD-TIME parse of JSX source only): ONE engine, two artifacts —
+`rust` (native addon, default) and `wasm` (the same engine compiled to
+WebAssembly, shipped inside `@csszyx/core`). Identical output by construction
+(same source, gate-pinned) — the artifact only affects build speed. The native
+binary ships as per-platform optional deps (`@csszyx/core-*`); if it's missing
+(unsupported arch, omitted optional deps, cross-platform frozen lockfile) the
+DEFAULT `rust` auto-degrades to `wasm` with a one-time warning — builds still
+succeed with identical classes. An EXPLICIT `parser:'rust'` (config or
+`CSSZYX_PARSER=rust`) hard-fails instead. Don't tell users a missing native
+binary breaks csszyx or changes classes; tell them to ignore the warning or set
+`build.parser:'wasm'`. The former `'oxc'`/`'babel'` values were removed. The RUNTIME
 has no parser: `_sz`/`szr`/`szv`/`splitBox` are plain JS; `dynamic()` lowers an sz
 OBJECT via `@csszyx/compiler/browser` (pure JS, no JSX parsing).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@csszyx/mcp-server",
-  "version": "0.13.0",
+  "version": "0.14.1",
   "description": "Model Context Protocol (MCP) server for csszyx — enables AI agents to understand and generate sz props",
   "license": "MIT",
   "type": "module",
@@ -30,13 +30,13 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.4.3",
-    "@csszyx/compiler": "0.13.0",
-    "@csszyx/cli": "0.13.0",
-    "@csszyx/unplugin": "0.13.0"
+    "@csszyx/cli": "0.14.1",
+    "@csszyx/compiler": "0.14.1",
+    "@csszyx/unplugin": "0.14.1"
   },
   "devDependencies": {
     "@types/node": "^22.20.1",
-    "tsx": "^4.23.1",
+    "tsx": "^4.23.11",
     "typescript": "^6.0.3",
     "unbuild": "^3.6.1",
     "vitest": "^4.1.10"