@bamboocss/parser 1.33.0 → 1.34.1

package/dist/index.cjs

@@ -884,6 +884,15 @@ var ParserResult = class {
 	* absent from the element — silently. Only the surprising half is collected; see `setCss`.
 	*/
 	unresolved = [];
+	/**
+	* Calls to a name the pattern or recipe entrypoint no longer exports.
+	*
+	* Separate from `unresolved`, which grades a call the build *did* see and could only
+	* partly resolve. These it saw and could not resolve at all: the binding is dead, so every
+	* rule the call would have contributed is absent rather than incomplete. Reported by
+	* `assertNoDeadCalls` rather than warned about, for that reason.
+	*/
+	deadCalls = [];
 	constructor(context, encoder) {
 		this.context = context;
 		this.encoder = encoder ?? context.encoder;
@@ -1261,6 +1270,7 @@ function createParser(context) {
 				}
 			});
 		});
+		parserResult.deadCalls = file.getDeadCalls();
 		return parserResult;
 	};
 }

package/dist/index.d.cts

@@ -1,4 +1,4 @@
-import { Context, ParserOptions, StyleDecoder, Stylesheet } from "@bamboocss/core";
+import { Context, DeadImport, ParserOptions, StyleDecoder, Stylesheet } from "@bamboocss/core";
 import { ArtifactId, BambooHooks, ConfigTsOptions, CssArtifactType, LoadConfigResult, ParserResultConfigureOptions, ParserResultInterface, ResultItem, Runtime, SpecFile, SpecType, SpecTypeMap } from "@bamboocss/types";
 import { FileSystemRefreshResult, Project as Project$1, ProjectOptions as ProjectOptions$1, SourceFile } from "ts-morph";
 
@@ -39,10 +39,7 @@ declare class Generator extends Context {
    * `keep` carries references this cannot see for itself; see `collectTokenReferences`.
    */
   pruneTokens: (sheet: Stylesheet, keep?: Set<string>, tokensReachableFromJs?: boolean) => {
-    removed: number;
-    kept: number;
-    removedProperties?: undefined;
-  } | {
+    reachable: Set<string> | undefined;
     removed: number;
     removedProperties: number;
     kept: number;
@@ -65,8 +62,21 @@ declare class Generator extends Context {
    * unused for want of a utility to reference it.
    *
    * `keep` carries names this cannot see for itself; see `collectKeyframeReferences`.
+   *
+   * `reachableVars` is `pruneTokens`' answer about custom properties, which has to be handed
+   * over rather than re-derived here. A token kept by a reader outside the stylesheet — a
+   * `token()` call, a `prune.keepTokens` pattern, a theme, a `globalCss` export — is
+   * reachable to that pass and invisible to this one, so deriving it again from the css
+   * deletes the `@keyframes` out from under a declaration that ships. Every caller that
+   * prunes both hands it over.
+   *
+   * Omitting it falls back to what `prune.tokens` implies. Under `off` that is `'all'`: no
+   * token declaration is removable, so each one ships and keeps the keyframe it names —
+   * and `off` is precisely the setting chosen because something outside the stylesheet
+   * reads them. Otherwise it is the css alone, which is what a caller running this pass
+   * without the other one is asking for.
    */
-  pruneKeyframes: (sheet: Stylesheet, keep?: Set<string>) => {
+  pruneKeyframes: (sheet: Stylesheet, keep?: Set<string>, reachableVars?: Set<string> | "all") => {
     removed: number;
     kept: number;
   } | undefined;
@@ -121,6 +131,51 @@ declare class Generator extends Context {
   private getAlwaysKeptTokenVars;
   getParserCss: (decoder: StyleDecoder) => string;
   getCss: (stylesheet?: Stylesheet) => string;
+  /**
+   * Fail on a style value shaped like a token path that names no token.
+   *
+   * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
+   * dead binding is not.
+   *
+   * Two sources, because neither sees the whole build.
+   *
+   * **Atomic styles are read off the decoded sheet** rather than accumulated as `transform`
+   * runs, and that is the load-bearing part for them. A `Context` outlives rebuilds while the
+   * decoder memoizes each atom by hash, so on the second build of the same source `transform`
+   * is never re-entered: an accumulating record either keeps a finding past the edit that
+   * fixed it — wedging a dev server — or is cleared and then never refilled, which passes a
+   * build whose source is still broken. That second one is the worse failure and is what an
+   * earlier version of this did.
+   *
+   * `decoder.atomic` has neither problem, because it is not a record of what happened — it is
+   * what the sheet is built from, and each result keeps the `prop` and `value` it was written
+   * with. So the question asked is the one that matters: does the stylesheet *being emitted*
+   * contain a declaration the browser will drop.
+   *
+   * Within a watch process that set is cumulative, and so is the css: extraction is additive,
+   * so the rule for a style deleted from source is still in the sheet until the process
+   * restarts. This reports the same way for the same reason — the declaration really is still
+   * in the file being written, and saying otherwise would be a check that disagreed with its
+   * own output. A production build is a fresh process and sees only what its source asked
+   * for.
+   *
+   * **Config-derived styles are not in that set at all**, which is the gap this used to have.
+   * `globalCss`, the reset, config recipes and compositions serialize through
+   * `transformStyles`, and that clones the decoder — so their atoms land in a throwaway and
+   * `decoder.atomic` never hears about them. Reading only the sheet made `'error'` *quieter*
+   * than the default on exactly those styles: the warning was suppressed in favour of a check
+   * that could not see them, so a bad token in `globalCss` warned with the option unset and
+   * then passed silently with it set to `'error'`. `utility.unresolvedTokens` is the record of
+   * what only `transform` can see; see it for why accumulating is right for that half.
+   *
+   * Both halves key on `property:path` with shorthands resolved, so a value that does reach
+   * both — every atomic style is transformed once before it is memoized — is one finding.
+   *
+   * Here rather than beside the asserts in `BambooContext` because this is where the sheet
+   * exists: those all run during extraction, before anything has been decoded. Every path
+   * that emits css comes through `getCss`.
+   */
+  assertNoUnresolvedTokens: () => void;
   /**
    * Get CSS for a specific layer from the stylesheet
    */
@@ -211,6 +266,15 @@ declare class ParserResult implements ParserResultInterface {
    * absent from the element — silently. Only the surprising half is collected; see `setCss`.
    */
   unresolved: UnresolvedStyle[];
+  /**
+   * Calls to a name the pattern or recipe entrypoint no longer exports.
+   *
+   * Separate from `unresolved`, which grades a call the build *did* see and could only
+   * partly resolve. These it saw and could not resolve at all: the binding is dead, so every
+   * rule the call would have contributed is absent rather than incomplete. Reported by
+   * `assertNoDeadCalls` rather than warned about, for that reason.
+   */
+  deadCalls: DeadImport[];
   constructor(context: ParserOptions, encoder?: ParserOptions['encoder']);
   append(result: ResultItem): ResultItem;
   set(name: 'cva' | 'css' | 'sva' | 'token', result: ResultItem): void;

package/dist/index.d.mts

@@ -1,5 +1,5 @@
 import { FileSystemRefreshResult, Project as Project$1, ProjectOptions as ProjectOptions$1, SourceFile } from "ts-morph";
-import { Context, ParserOptions, StyleDecoder, Stylesheet } from "@bamboocss/core";
+import { Context, DeadImport, ParserOptions, StyleDecoder, Stylesheet } from "@bamboocss/core";
 import { ArtifactId, BambooHooks, ConfigTsOptions, CssArtifactType, LoadConfigResult, ParserResultConfigureOptions, ParserResultInterface, ResultItem, Runtime, SpecFile, SpecType, SpecTypeMap } from "@bamboocss/types";
 
 //#region ../generator/dist/index.d.cts
@@ -39,10 +39,7 @@ declare class Generator extends Context {
    * `keep` carries references this cannot see for itself; see `collectTokenReferences`.
    */
   pruneTokens: (sheet: Stylesheet, keep?: Set<string>, tokensReachableFromJs?: boolean) => {
-    removed: number;
-    kept: number;
-    removedProperties?: undefined;
-  } | {
+    reachable: Set<string> | undefined;
     removed: number;
     removedProperties: number;
     kept: number;
@@ -65,8 +62,21 @@ declare class Generator extends Context {
    * unused for want of a utility to reference it.
    *
    * `keep` carries names this cannot see for itself; see `collectKeyframeReferences`.
+   *
+   * `reachableVars` is `pruneTokens`' answer about custom properties, which has to be handed
+   * over rather than re-derived here. A token kept by a reader outside the stylesheet — a
+   * `token()` call, a `prune.keepTokens` pattern, a theme, a `globalCss` export — is
+   * reachable to that pass and invisible to this one, so deriving it again from the css
+   * deletes the `@keyframes` out from under a declaration that ships. Every caller that
+   * prunes both hands it over.
+   *
+   * Omitting it falls back to what `prune.tokens` implies. Under `off` that is `'all'`: no
+   * token declaration is removable, so each one ships and keeps the keyframe it names —
+   * and `off` is precisely the setting chosen because something outside the stylesheet
+   * reads them. Otherwise it is the css alone, which is what a caller running this pass
+   * without the other one is asking for.
    */
-  pruneKeyframes: (sheet: Stylesheet, keep?: Set<string>) => {
+  pruneKeyframes: (sheet: Stylesheet, keep?: Set<string>, reachableVars?: Set<string> | "all") => {
     removed: number;
     kept: number;
   } | undefined;
@@ -121,6 +131,51 @@ declare class Generator extends Context {
   private getAlwaysKeptTokenVars;
   getParserCss: (decoder: StyleDecoder) => string;
   getCss: (stylesheet?: Stylesheet) => string;
+  /**
+   * Fail on a style value shaped like a token path that names no token.
+   *
+   * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
+   * dead binding is not.
+   *
+   * Two sources, because neither sees the whole build.
+   *
+   * **Atomic styles are read off the decoded sheet** rather than accumulated as `transform`
+   * runs, and that is the load-bearing part for them. A `Context` outlives rebuilds while the
+   * decoder memoizes each atom by hash, so on the second build of the same source `transform`
+   * is never re-entered: an accumulating record either keeps a finding past the edit that
+   * fixed it — wedging a dev server — or is cleared and then never refilled, which passes a
+   * build whose source is still broken. That second one is the worse failure and is what an
+   * earlier version of this did.
+   *
+   * `decoder.atomic` has neither problem, because it is not a record of what happened — it is
+   * what the sheet is built from, and each result keeps the `prop` and `value` it was written
+   * with. So the question asked is the one that matters: does the stylesheet *being emitted*
+   * contain a declaration the browser will drop.
+   *
+   * Within a watch process that set is cumulative, and so is the css: extraction is additive,
+   * so the rule for a style deleted from source is still in the sheet until the process
+   * restarts. This reports the same way for the same reason — the declaration really is still
+   * in the file being written, and saying otherwise would be a check that disagreed with its
+   * own output. A production build is a fresh process and sees only what its source asked
+   * for.
+   *
+   * **Config-derived styles are not in that set at all**, which is the gap this used to have.
+   * `globalCss`, the reset, config recipes and compositions serialize through
+   * `transformStyles`, and that clones the decoder — so their atoms land in a throwaway and
+   * `decoder.atomic` never hears about them. Reading only the sheet made `'error'` *quieter*
+   * than the default on exactly those styles: the warning was suppressed in favour of a check
+   * that could not see them, so a bad token in `globalCss` warned with the option unset and
+   * then passed silently with it set to `'error'`. `utility.unresolvedTokens` is the record of
+   * what only `transform` can see; see it for why accumulating is right for that half.
+   *
+   * Both halves key on `property:path` with shorthands resolved, so a value that does reach
+   * both — every atomic style is transformed once before it is memoized — is one finding.
+   *
+   * Here rather than beside the asserts in `BambooContext` because this is where the sheet
+   * exists: those all run during extraction, before anything has been decoded. Every path
+   * that emits css comes through `getCss`.
+   */
+  assertNoUnresolvedTokens: () => void;
   /**
    * Get CSS for a specific layer from the stylesheet
    */
@@ -211,6 +266,15 @@ declare class ParserResult implements ParserResultInterface {
    * absent from the element — silently. Only the surprising half is collected; see `setCss`.
    */
   unresolved: UnresolvedStyle[];
+  /**
+   * Calls to a name the pattern or recipe entrypoint no longer exports.
+   *
+   * Separate from `unresolved`, which grades a call the build *did* see and could only
+   * partly resolve. These it saw and could not resolve at all: the binding is dead, so every
+   * rule the call would have contributed is absent rather than incomplete. Reported by
+   * `assertNoDeadCalls` rather than warned about, for that reason.
+   */
+  deadCalls: DeadImport[];
   constructor(context: ParserOptions, encoder?: ParserOptions['encoder']);
   append(result: ResultItem): ResultItem;
   set(name: 'cva' | 'css' | 'sva' | 'token', result: ResultItem): void;

package/dist/index.mjs

@@ -883,6 +883,15 @@ var ParserResult = class {
 	* absent from the element — silently. Only the surprising half is collected; see `setCss`.
 	*/
 	unresolved = [];
+	/**
+	* Calls to a name the pattern or recipe entrypoint no longer exports.
+	*
+	* Separate from `unresolved`, which grades a call the build *did* see and could only
+	* partly resolve. These it saw and could not resolve at all: the binding is dead, so every
+	* rule the call would have contributed is absent rather than incomplete. Reported by
+	* `assertNoDeadCalls` rather than warned about, for that reason.
+	*/
+	deadCalls = [];
 	constructor(context, encoder) {
 		this.context = context;
 		this.encoder = encoder ?? context.encoder;
@@ -1260,6 +1269,7 @@ function createParser(context) {
 				}
 			});
 		});
+		parserResult.deadCalls = file.getDeadCalls();
 		return parserResult;
 	};
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamboocss/parser",
-  "version": "1.33.0",
+  "version": "1.34.1",
   "description": "The static parser for bamboo css",
   "homepage": "https://bamboocss.com",
   "license": "MIT",
@@ -34,17 +34,17 @@
   "dependencies": {
     "ts-morph": "28.0.0",
     "ts-pattern": "5.9.0",
-    "@bamboocss/config": "^1.33.0",
-    "@bamboocss/core": "^1.33.0",
-    "@bamboocss/extractor": "1.33.0",
-    "@bamboocss/logger": "1.33.0",
-    "@bamboocss/shared": "1.33.0",
-    "@bamboocss/types": "1.33.0"
+    "@bamboocss/config": "^1.34.1",
+    "@bamboocss/core": "^1.34.1",
+    "@bamboocss/extractor": "1.34.1",
+    "@bamboocss/logger": "1.34.1",
+    "@bamboocss/shared": "1.34.1",
+    "@bamboocss/types": "1.34.1"
   },
   "devDependencies": {
-    "@bamboocss/generator": "1.33.0",
-    "@bamboocss/plugin-svelte": "1.33.0",
-    "@bamboocss/plugin-vue": "1.33.0"
+    "@bamboocss/generator": "1.34.1",
+    "@bamboocss/plugin-svelte": "1.34.1",
+    "@bamboocss/plugin-vue": "1.34.1"
   },
   "scripts": {
     "build": "tsdown src/index.ts --format=esm,cjs --dts",