@bamboocss/types 1.21.0 → 1.23.0

package/dist/config.d.ts

@@ -277,6 +277,15 @@ interface CssgenOptions {
   separator?: '_' | '=' | '-'
   /**
    * Whether to minify the generated css.
+   *
+   * Worth about 21% of the raw stylesheet and 5–7% gzipped on the example apps here. The
+   * gzip figure is the smaller one because compression has already collapsed the indentation
+   * before you get there — but unlike renaming what is emitted, it never comes out negative.
+   *
+   * Off by default so the generated stylesheet stays readable, and because most projects
+   * hand it to a bundler that minifies css in production anyway. Worth turning on if you
+   * ship `styled-system/styles.css` directly, or pass `--minify` to the CLI for one build.
+   *
    * @default false
    */
   minify?: boolean
@@ -314,7 +323,21 @@ interface CssgenOptions {
    * negative token resolves to `calc(var(--spacing-4) * -1)`, so every token with a
    * negative counterpart pins its own declaration. Spacing scales generate one per entry,
    * which keeps the whole scale whether or not the app uses it — on the default preset
-   * that is roughly a third of what survives pruning. There is no opt-out.
+   * that is roughly a third of what survives pruning.
+   *
+   * That exemption is now skipped entirely for a project that never reaches for a token from
+   * javascript. The tokens artifact is generated into the project rather than installed, so
+   * the import is written in your own source and a scan of `include` finds it — a call, or an
+   * import of any module the artifact could be. On the example apps here that is worth up to
+   * 20% of the stylesheet raw and 13% gzipped, and nothing at all on the one that does call
+   * `token()`, which is the point: a project with a caller keeps every declaration.
+   *
+   * The scan reads `include`, which scopes style extraction rather than everything that may
+   * import — so a script, a config, or a sibling workspace package that calls `token()` is
+   * not covered, nor is a binding renamed away from `token`, as in `const t = token`. Both
+   * are rare and neither reports itself: the declaration goes and the call returns a `var()`
+   * nothing declares. Setting this to `false` keeps every declaration if you are in that
+   * position.
    *
    * Setting this to `false` keeps every token declaration, but still drops the `@property`
    * registrations. Those are not tokens — nothing hands one to javascript and none appear
@@ -341,6 +364,37 @@ interface CssgenOptions {
    * @default true
    */
   pruneUnusedKeyframes?: boolean
+  /**
+   * Whether to drop the parts of the reset that style elements your source never renders.
+   *
+   * Two thirds of the reset is bound to specific elements — 41 of them, covering `table`,
+   * `pre`, `kbd`, `optgroup` and the rest of the long tail. The reset is a fixed size, so it
+   * dominates a small stylesheet: a third of one sandbox's css here and four fifths of
+   * another's, of which 13% and 34% respectively is for elements those projects never render.
+   *
+   * A selector list loses only the parts naming unrendered elements, so a rule shared between
+   * `button` and `::file-selector-button` keeps the half that still applies. `html` and `body`
+   * are never removed.
+   *
+   * Off by default, and it cannot be made safe by default. Unlike the token and keyframe
+   * passes there is nothing to prove this against: an element rendered by a dependency's
+   * component, by `dangerouslySetInnerHTML`, or by markdown is invisible to a scan of your own
+   * source. What you get wrong is an element quietly losing its reset — no error, no warning.
+   * Reach for it when you control the markup and have measured that it pays.
+   *
+   * The blind spot to check first is your own entry template. The scan reads `include`, and
+   * `include` conventionally covers components rather than markup — a glob rooted at `./src`
+   * does not match `index.html`, so an element appearing only there is dropped. Add the
+   * template to `include` to cover it — the scan reads any file listed, not only ones the
+   * parser understands, and reads it from disk rather than from the build's parsed copy, so
+   * a single-file component's markup survives the transform to tsx.
+   *
+   * A scoped reset is handled: `preflight: { scope: '.app' }` writes `.app table`, and the
+   * scope is stripped before an element is read out. `bamboo cssgen preflight` prunes too.
+   *
+   * @default false
+   */
+  prunePreflight?: boolean
   /**
    * The root selector for the css variables.
    * @default ':where(:host, :root)'
@@ -410,19 +464,6 @@ interface CodegenOptions {
    * @default false
    */
   forceConsistentTypeExtension?: boolean
-  /**
-   * Controls how CSS utility classes are generated.
-   * - `'atomic'` (default): one class per property (e.g. `c_red p_8px`)
-   * - `'grouped'`: one class per `css()` call, grouping all properties together
-   *
-   * Grouped mode reduces the number of classes in the HTML at the cost of potential CSS duplication.
-   *
-   * A grouped class names a whole call, so the build has to have seen that exact call to emit its rule.
-   * Where it cannot, the runtime falls back to atomic class names — and a few shapes lose their styles
-   * entirely, without a warning. Read https://bamboocss.com/docs/references/config#cssmode before enabling it.
-   * @default 'atomic'
-   */
-  cssMode?: 'atomic' | 'grouped'
 }
 
 interface PresetOptions {

package/dist/hooks-api.d.ts

@@ -12,10 +12,6 @@ export interface AtomicRule extends BaseRule {
   styles: SystemStyleObject
 }
 
-export interface GroupedRule extends BaseRule {
-  styles: SystemStyleObject
-}
-
 export interface AtomicRecipeRule extends BaseRule {
   config: RecipeDefinition<any> | SlotRecipeDefinition<string, any>
 }
@@ -26,7 +22,6 @@ export interface RecipeVariantsRule extends BaseRule {
 
 export interface ProcessorInterface {
   css(styles: SystemStyleObject): AtomicRule
-  grouped(styles: SystemStyleObject): GroupedRule
   cva(recipeConfig: RecipeDefinition<RecipeVariantRecord>): AtomicRecipeRule
   sva(recipeConfig: SlotRecipeDefinition<string, SlotRecipeVariantRecord<string>>): AtomicRecipeRule
   recipe(name: string, variants?: RecipeVariantRecord): RecipeVariantsRule | undefined

package/dist/parser.d.ts

@@ -3,7 +3,7 @@ import type { BoxNodeArray, BoxNodeLiteral, BoxNodeMap, Unboxed } from '@bambooc
 export interface ResultItem {
   name?: string
   data: Array<Unboxed['raw']>
-  type?: 'css' | 'cva' | 'sva' | 'token' | 'pattern' | 'recipe' | 'jsx-recipe'
+  type?: 'css' | 'cva' | 'sva' | 'token' | 'pattern' | 'recipe' | 'jsx-recipe' | 'cva-call'
   box?: BoxNodeMap | BoxNodeLiteral | BoxNodeArray
 }
 
@@ -11,6 +11,8 @@ export interface ParserResultInterface {
   all: Array<ResultItem>
   css: Set<ResultItem>
   cva: Set<ResultItem>
+  /** Calls of a locally-bound inline recipe: `const b = cva(...)`, then `b({ ... })`. */
+  cvaCall: Set<ResultItem>
   sva: Set<ResultItem>
   token: Set<ResultItem>
   viewTransition: Set<ResultItem>
@@ -36,9 +38,6 @@ export interface EncoderJson {
     recipes?: {
       [name: string]: string[]
     }
-    grouped?: {
-      [groupId: string]: string[]
-    }
     /** Bag class -> the `::view-transition-*` slot styles behind it. */
     viewTransitions?: {
       [className: string]: Record<string, any>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamboocss/types",
-  "version": "1.21.0",
+  "version": "1.23.0",
   "description": "The types for css bamboo",
   "homepage": "https://bamboocss.com",
   "license": "MIT",
@@ -32,7 +32,7 @@
     "ncp": "2.0.0",
     "pkg-types": "2.3.0",
     "ts-morph": "28.0.0",
-    "@bamboocss/extractor": "1.21.0"
+    "@bamboocss/extractor": "1.23.0"
   },
   "scripts": {
     "dev": "tsx scripts/watch.ts",