@bamboocss/vite 1.14.0 → 1.16.0

package/dist/index.d.cts

@@ -31,9 +31,18 @@ declare const createRuntimeCss: (ctx: Context) => RuntimeCss;
  * Why a call site was left alone. Surfaced through `panda`-style diagnostics so a
  * user can tell the difference between "this folded" and "this silently didn't".
  */
-type SkipReason = 'dynamic' | 'raw-call' | 'not-foldable' | 'unsupported-kind' | 'not-imported' | 'no-call-expression' | 'overlapping' | 'empty';
+type SkipReason = 'dynamic' | 'raw-call' | 'not-foldable' | 'unsupported-kind' | 'not-imported' | 'no-call-expression' | 'overlapping' | 'empty' | 'unresolved-token';
 interface FoldedCall {
   name: string;
+  /**
+   * What the call collapsed to.
+   *
+   * `class` is every style surface: a class string bound for a `class` attribute. `value`
+   * is `token()`, which resolves to a CSS *value* (`var(--colors-red-300)`). The two are
+   * not interchangeable, and a consumer that checks folded classes against the emitted
+   * stylesheet has to skip the latter — there is no rule named after a variable reference.
+   */
+  kind: 'class' | 'value';
   /** The class string resolved outright, empty when the whole call lowered to ternaries. */
   className: string;
   /**
@@ -42,6 +51,8 @@ interface FoldedCall {
    * which `className` alone does not carry.
    */
   classNames: string[];
+  /** The literal written in place of the call, for a `value` fold. */
+  value?: string;
   start: number;
   end: number;
 }
@@ -75,13 +86,8 @@ interface FoldOptions {
   /** Reuse one runtime `css` across files in a build. */
   runtimeCss?: RuntimeCss;
   /**
-   * Also collapse `styled.*` and pattern elements to the tag they render. On by default,
-   * since the JSX factory is where most style resolution happens at runtime.
-   */
-  jsx?: boolean;
-  /**
-   * Split a `css()` call or a `styled.*` element that is only partly static, keeping the
-   * dynamic half at runtime. On by default.
+   * Split a `css()` call that is only partly static, keeping the dynamic half at runtime.
+   * On by default.
    */
   partial?: boolean;
 }
@@ -98,16 +104,6 @@ interface BambooVitePluginOptions {
    * @default false
    */
   transform?: boolean;
-  /**
-   * Also collapse `styled.*` and pattern elements to the tag they render, rather than
-   * folding call sites alone.
-   *
-   * On by default, and the larger of the two wins: the factory runs `splitProps`,
-   * `css()` and `cx` for every element on every render, inside a `forwardRef` component.
-   *
-   * @default true
-   */
-  jsx?: boolean;
   /**
    * Split a call or element that is only partly static, so the resolvable half becomes a
    * literal and only the rest keeps its runtime call. On by default.

package/dist/index.d.mts

@@ -31,9 +31,18 @@ declare const createRuntimeCss: (ctx: Context) => RuntimeCss;
  * Why a call site was left alone. Surfaced through `panda`-style diagnostics so a
  * user can tell the difference between "this folded" and "this silently didn't".
  */
-type SkipReason = 'dynamic' | 'raw-call' | 'not-foldable' | 'unsupported-kind' | 'not-imported' | 'no-call-expression' | 'overlapping' | 'empty';
+type SkipReason = 'dynamic' | 'raw-call' | 'not-foldable' | 'unsupported-kind' | 'not-imported' | 'no-call-expression' | 'overlapping' | 'empty' | 'unresolved-token';
 interface FoldedCall {
   name: string;
+  /**
+   * What the call collapsed to.
+   *
+   * `class` is every style surface: a class string bound for a `class` attribute. `value`
+   * is `token()`, which resolves to a CSS *value* (`var(--colors-red-300)`). The two are
+   * not interchangeable, and a consumer that checks folded classes against the emitted
+   * stylesheet has to skip the latter — there is no rule named after a variable reference.
+   */
+  kind: 'class' | 'value';
   /** The class string resolved outright, empty when the whole call lowered to ternaries. */
   className: string;
   /**
@@ -42,6 +51,8 @@ interface FoldedCall {
    * which `className` alone does not carry.
    */
   classNames: string[];
+  /** The literal written in place of the call, for a `value` fold. */
+  value?: string;
   start: number;
   end: number;
 }
@@ -75,13 +86,8 @@ interface FoldOptions {
   /** Reuse one runtime `css` across files in a build. */
   runtimeCss?: RuntimeCss;
   /**
-   * Also collapse `styled.*` and pattern elements to the tag they render. On by default,
-   * since the JSX factory is where most style resolution happens at runtime.
-   */
-  jsx?: boolean;
-  /**
-   * Split a `css()` call or a `styled.*` element that is only partly static, keeping the
-   * dynamic half at runtime. On by default.
+   * Split a `css()` call that is only partly static, keeping the dynamic half at runtime.
+   * On by default.
    */
   partial?: boolean;
 }
@@ -98,16 +104,6 @@ interface BambooVitePluginOptions {
    * @default false
    */
   transform?: boolean;
-  /**
-   * Also collapse `styled.*` and pattern elements to the tag they render, rather than
-   * folding call sites alone.
-   *
-   * On by default, and the larger of the two wins: the factory runs `splitProps`,
-   * `css()` and `cx` for every element on every render, inside a `forwardRef` component.
-   *
-   * @default true
-   */
-  jsx?: boolean;
   /**
    * Split a call or element that is only partly static, so the resolvable half becomes a
    * literal and only the rest keeps its runtime call. On by default.