@bamboocss/generator 1.34.0 → 1.34.1

package/dist/index.cjs

@@ -4097,13 +4097,15 @@ var Generator = class extends _bamboocss_core.Context {
 	* Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
 	* dead binding is not.
 	*
-	* Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
-	* load-bearing part. 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.
+	* 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
@@ -4117,22 +4119,35 @@ var Generator = class extends _bamboocss_core.Context {
 	* 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 = () => {
 		if (this.config.unresolvedToken !== "error") return;
-		const found = /* @__PURE__ */ new Map();
+		const found = new Map(this.utility.unresolvedTokens);
 		for (const atom of this.decoder.atomic) {
 			const { prop, value } = atom.entry;
 			if (typeof value !== "string" || typeof prop !== "string") continue;
 			if (!this.utility.isUnresolvedTokenValue(prop, value)) continue;
-			const bare = this.utility.bareTokenPath(prop, value);
-			found.set(`${prop}:${bare}`, {
-				prop,
+			const key = this.utility.resolveShorthand(prop);
+			const bare = this.utility.bareTokenPath(key, value);
+			found.set(`${key}:${bare}`, {
+				prop: key,
 				value: bare,
-				category: this.utility.getTokenCategory(prop)
+				category: this.utility.getTokenCategory(key)
 			});
 		}
 		if (!found.size) return;

package/dist/index.d.cts

@@ -135,13 +135,15 @@ declare class Generator extends Context {
    * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
    * dead binding is not.
    *
-   * Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
-   * load-bearing part. 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.
+   * 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
@@ -155,6 +157,18 @@ declare class Generator extends Context {
    * 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`.

package/dist/index.d.mts

@@ -135,13 +135,15 @@ declare class Generator extends Context {
    * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
    * dead binding is not.
    *
-   * Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
-   * load-bearing part. 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.
+   * 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
@@ -155,6 +157,18 @@ declare class Generator extends Context {
    * 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`.

package/dist/index.mjs

@@ -4071,13 +4071,15 @@ var Generator = class extends Context {
 	* Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
 	* dead binding is not.
 	*
-	* Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
-	* load-bearing part. 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.
+	* 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
@@ -4091,22 +4093,35 @@ var Generator = class extends Context {
 	* 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 = () => {
 		if (this.config.unresolvedToken !== "error") return;
-		const found = /* @__PURE__ */ new Map();
+		const found = new Map(this.utility.unresolvedTokens);
 		for (const atom of this.decoder.atomic) {
 			const { prop, value } = atom.entry;
 			if (typeof value !== "string" || typeof prop !== "string") continue;
 			if (!this.utility.isUnresolvedTokenValue(prop, value)) continue;
-			const bare = this.utility.bareTokenPath(prop, value);
-			found.set(`${prop}:${bare}`, {
-				prop,
+			const key = this.utility.resolveShorthand(prop);
+			const bare = this.utility.bareTokenPath(key, value);
+			found.set(`${key}:${bare}`, {
+				prop: key,
 				value: bare,
-				category: this.utility.getTokenCategory(prop)
+				category: this.utility.getTokenCategory(key)
 			});
 		}
 		if (!found.size) return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamboocss/generator",
-  "version": "1.34.0",
+  "version": "1.34.1",
   "description": "The css generator for css bamboo",
   "homepage": "https://bamboocss.com",
   "license": "MIT",
@@ -38,12 +38,12 @@
     "pluralize": "8.0.0",
     "postcss": "8.5.26",
     "ts-pattern": "5.9.0",
-    "@bamboocss/core": "1.34.0",
-    "@bamboocss/logger": "1.34.0",
-    "@bamboocss/token-dictionary": "1.34.0",
-    "@bamboocss/is-valid-prop": "^1.34.0",
-    "@bamboocss/shared": "1.34.0",
-    "@bamboocss/types": "1.34.0"
+    "@bamboocss/core": "1.34.1",
+    "@bamboocss/is-valid-prop": "^1.34.1",
+    "@bamboocss/logger": "1.34.1",
+    "@bamboocss/shared": "1.34.1",
+    "@bamboocss/token-dictionary": "1.34.1",
+    "@bamboocss/types": "1.34.1"
   },
   "devDependencies": {
     "@types/pluralize": "0.0.33"