@bamboocss/generator 1.14.0 → 1.16.0

package/dist/index.d.cts

@@ -91,6 +91,20 @@ declare class Generator extends Context {
    */
   private getAlwaysKeptTokenVars;
   getParserCss: (decoder: StyleDecoder) => string;
+  /**
+   * The grouped class names this build emitted a rule for.
+   *
+   * Derived from the encoder rather than the decoder, so it is available as soon as
+   * extraction finishes and before a stylesheet exists. Both sides go through
+   * `groupClassName`, which is the same function the browser runtime calls — a registry
+   * built any other way would be a third spelling of a name that already has two.
+   *
+   * Unescaped, unlike `StyleDecoder`'s class names: this is compared against what `css()`
+   * returns into a `class` attribute, not against a selector. A grouped class is an opaque
+   * hash, so the two only differ in principle, but the principle is the one that matters
+   * here — the registry is only useful if it holds exactly what the runtime will ask about.
+   */
+  getGroupRegistry: () => string[];
   getCss: (stylesheet?: Stylesheet) => string;
   /**
    * Get CSS for a specific layer from the stylesheet
@@ -119,4 +133,27 @@ declare class Generator extends Context {
  */
 declare function getThemeCss(ctx: Context, themeName: string): string;
 //#endregion
-export { Generator, SplitCssArtifact, SplitCssResult, getThemeCss };
+//#region src/artifacts/js/group-registry.d.ts
+/**
+ * The grouped classes the build emitted a rule for.
+ *
+ * Under `cssMode: 'grouped'` a class names a whole `css()` call, so the build has to have
+ * seen that exact call to emit its rule. This is how the runtime tells the difference: a
+ * class in here has CSS behind it, and one that is not falls back to naming its
+ * declarations atomically as well.
+ *
+ * Written by two passes. `codegen` emits whatever the encoder already holds — usually
+ * nothing, since it runs on config change before anything is extracted, but not blank when
+ * it runs after a build. The CSS build then rewrites it with the set it emitted.
+ *
+ * An empty or stale registry is safe by construction: the runtime *adds* to the group class
+ * rather than replacing it, so the worst a miss can do is name a class that matches nothing.
+ */
+declare function generateGroupRegistry(ctx: Pick<Context, 'encoder' | 'utility'>, classNames?: string[]): {
+  js: string;
+  dts: string;
+};
+/** Where the registry lives, so the writer and the importer cannot disagree about it. */
+declare const GROUP_REGISTRY_FILE = "groups";
+//#endregion
+export { GROUP_REGISTRY_FILE, Generator, SplitCssArtifact, SplitCssResult, generateGroupRegistry, getThemeCss };

package/dist/index.d.mts

@@ -91,6 +91,20 @@ declare class Generator extends Context {
    */
   private getAlwaysKeptTokenVars;
   getParserCss: (decoder: StyleDecoder) => string;
+  /**
+   * The grouped class names this build emitted a rule for.
+   *
+   * Derived from the encoder rather than the decoder, so it is available as soon as
+   * extraction finishes and before a stylesheet exists. Both sides go through
+   * `groupClassName`, which is the same function the browser runtime calls — a registry
+   * built any other way would be a third spelling of a name that already has two.
+   *
+   * Unescaped, unlike `StyleDecoder`'s class names: this is compared against what `css()`
+   * returns into a `class` attribute, not against a selector. A grouped class is an opaque
+   * hash, so the two only differ in principle, but the principle is the one that matters
+   * here — the registry is only useful if it holds exactly what the runtime will ask about.
+   */
+  getGroupRegistry: () => string[];
   getCss: (stylesheet?: Stylesheet) => string;
   /**
    * Get CSS for a specific layer from the stylesheet
@@ -119,4 +133,27 @@ declare class Generator extends Context {
  */
 declare function getThemeCss(ctx: Context, themeName: string): string;
 //#endregion
-export { Generator, SplitCssArtifact, SplitCssResult, getThemeCss };
+//#region src/artifacts/js/group-registry.d.ts
+/**
+ * The grouped classes the build emitted a rule for.
+ *
+ * Under `cssMode: 'grouped'` a class names a whole `css()` call, so the build has to have
+ * seen that exact call to emit its rule. This is how the runtime tells the difference: a
+ * class in here has CSS behind it, and one that is not falls back to naming its
+ * declarations atomically as well.
+ *
+ * Written by two passes. `codegen` emits whatever the encoder already holds — usually
+ * nothing, since it runs on config change before anything is extracted, but not blank when
+ * it runs after a build. The CSS build then rewrites it with the set it emitted.
+ *
+ * An empty or stale registry is safe by construction: the runtime *adds* to the group class
+ * rather than replacing it, so the worst a miss can do is name a class that matches nothing.
+ */
+declare function generateGroupRegistry(ctx: Pick<Context, 'encoder' | 'utility'>, classNames?: string[]): {
+  js: string;
+  dts: string;
+};
+/** Where the registry lives, so the writer and the importer cannot disagree about it. */
+declare const GROUP_REGISTRY_FILE = "groups";
+//#endregion
+export { GROUP_REGISTRY_FILE, Generator, SplitCssArtifact, SplitCssResult, generateGroupRegistry, getThemeCss };