@bamboocss/config 1.43.1 → 1.44.0

package/dist/index.cjs

@@ -865,7 +865,7 @@ const validateRecipes = (options) => {
 * upgrading across them.
 */
 const REMOVED = {
-	pruneUnusedTokens: (value) => value === "strict" ? `\`pruneUnusedTokens: 'strict'\` is now \`prune: { tokens: 'accounted', unresolvedPath: 'error' }\`.` : `\`pruneUnusedTokens\` is now \`prune: { tokens: '${value === false ? "off" : "reachable"}' }\`.`,
+	pruneUnusedTokens: (value) => value === "strict" ? `\`pruneUnusedTokens: 'strict'\` is now \`prune: { tokens: true, unresolvedPath: 'error' }\`.` : `\`pruneUnusedTokens\` is now \`prune: { tokens: ${value === false ? "false" : "true"} }\`.`,
 	pruneUnusedKeyframes: (value) => `\`pruneUnusedKeyframes\` is now \`prune: { keyframes: ${value === false ? "false" : "true"} }\`.`,
 	prunePreflight: (value) => `\`prunePreflight\` is now \`preflight: { prune: ${value === false ? "false" : "true"} }\`.`,
 	globalCss: () => `\`globalCss\` is now \`global: { css }\`.`,
@@ -884,7 +884,7 @@ const COMPOSITION_MOVED = (old, prop) => () => `\`theme.${old}\` is now \`theme.
 const REMOVED_NESTED = {
 	prune: {
 		preflight: (value) => `\`prune.preflight\` is now \`preflight: { prune: ${value === false ? "false" : "true"} }\`. It was a second key named \`preflight\` one level away from the one that emits the reset, so a config asked for a reset in one place and reshaped it in another — and pruning a scoped reset already had to read \`preflight.scope\` to work at all.`,
-		unresolved: (value) => `\`prune.unresolved\` is now \`prune.unresolvedPath\`, and the accounting pass it used to switch on is now \`prune.tokens: 'accounted'\` — write \`prune: { tokens: 'accounted', unresolvedPath: '${value === "error" ? "error" : "warn"}' }\`. They are separate because \`'off'\` used to mean two things at once: no accounting, and no report.`
+		unresolved: (value) => `\`prune.unresolved\` is now \`prune.unresolvedPath\` — write \`prune: { tokens: true, unresolvedPath: '${value === "error" ? "error" : "warn"}' }\`. The accounting pass it used to switch on runs by default now, so this only decides whether an unfollowable path is reported.`
 	},
 	theme: {
 		textStyles: COMPOSITION_MOVED("textStyles", "textStyle"),
@@ -939,7 +939,10 @@ function validateRemovedOptions(config, addError) {
 		const message = retired[value];
 		if (message) addError("config", message);
 	}
-	if (typeof dict.prune?.tokens === "boolean") addError("config", `\`prune.tokens\` takes a strategy now, not a boolean — write \`'${dict.prune.tokens ? "reachable" : "off"}'\`. \`'accounted'\` is the new one: keeps computed from the token paths in your source rather than from what the css reaches.`);
+	if (typeof dict.prune?.tokens === "string") {
+		const strategy = dict.prune.tokens;
+		addError("config", `\`prune.tokens\` takes a boolean now, not a strategy — write \`${strategy === "off" ? "false" : "true"}\`.${strategy === "reachable" ? ` \`true\` accounts for each token path individually rather than keeping every declaration the moment javascript reaches for one, so it prunes at least as much and usually far more.` : strategy === "accounted" ? ` That is what \`true\` does now; it stopped being something to opt into. Reporting moved to \`prune: { unresolvedPath: 'warn' }\`, which \`'accounted'\` used to imply.` : ""}`);
+	}
 	for (const [name, pattern] of Object.entries(config.patterns ?? {})) {
 		const dictPattern = pattern;
 		if (!dictPattern) continue;

package/dist/index.mjs

@@ -837,7 +837,7 @@ const validateRecipes = (options) => {
 * upgrading across them.
 */
 const REMOVED = {
-	pruneUnusedTokens: (value) => value === "strict" ? `\`pruneUnusedTokens: 'strict'\` is now \`prune: { tokens: 'accounted', unresolvedPath: 'error' }\`.` : `\`pruneUnusedTokens\` is now \`prune: { tokens: '${value === false ? "off" : "reachable"}' }\`.`,
+	pruneUnusedTokens: (value) => value === "strict" ? `\`pruneUnusedTokens: 'strict'\` is now \`prune: { tokens: true, unresolvedPath: 'error' }\`.` : `\`pruneUnusedTokens\` is now \`prune: { tokens: ${value === false ? "false" : "true"} }\`.`,
 	pruneUnusedKeyframes: (value) => `\`pruneUnusedKeyframes\` is now \`prune: { keyframes: ${value === false ? "false" : "true"} }\`.`,
 	prunePreflight: (value) => `\`prunePreflight\` is now \`preflight: { prune: ${value === false ? "false" : "true"} }\`.`,
 	globalCss: () => `\`globalCss\` is now \`global: { css }\`.`,
@@ -856,7 +856,7 @@ const COMPOSITION_MOVED = (old, prop) => () => `\`theme.${old}\` is now \`theme.
 const REMOVED_NESTED = {
 	prune: {
 		preflight: (value) => `\`prune.preflight\` is now \`preflight: { prune: ${value === false ? "false" : "true"} }\`. It was a second key named \`preflight\` one level away from the one that emits the reset, so a config asked for a reset in one place and reshaped it in another — and pruning a scoped reset already had to read \`preflight.scope\` to work at all.`,
-		unresolved: (value) => `\`prune.unresolved\` is now \`prune.unresolvedPath\`, and the accounting pass it used to switch on is now \`prune.tokens: 'accounted'\` — write \`prune: { tokens: 'accounted', unresolvedPath: '${value === "error" ? "error" : "warn"}' }\`. They are separate because \`'off'\` used to mean two things at once: no accounting, and no report.`
+		unresolved: (value) => `\`prune.unresolved\` is now \`prune.unresolvedPath\` — write \`prune: { tokens: true, unresolvedPath: '${value === "error" ? "error" : "warn"}' }\`. The accounting pass it used to switch on runs by default now, so this only decides whether an unfollowable path is reported.`
 	},
 	theme: {
 		textStyles: COMPOSITION_MOVED("textStyles", "textStyle"),
@@ -911,7 +911,10 @@ function validateRemovedOptions(config, addError) {
 		const message = retired[value];
 		if (message) addError("config", message);
 	}
-	if (typeof dict.prune?.tokens === "boolean") addError("config", `\`prune.tokens\` takes a strategy now, not a boolean — write \`'${dict.prune.tokens ? "reachable" : "off"}'\`. \`'accounted'\` is the new one: keeps computed from the token paths in your source rather than from what the css reaches.`);
+	if (typeof dict.prune?.tokens === "string") {
+		const strategy = dict.prune.tokens;
+		addError("config", `\`prune.tokens\` takes a boolean now, not a strategy — write \`${strategy === "off" ? "false" : "true"}\`.${strategy === "reachable" ? ` \`true\` accounts for each token path individually rather than keeping every declaration the moment javascript reaches for one, so it prunes at least as much and usually far more.` : strategy === "accounted" ? ` That is what \`true\` does now; it stopped being something to opt into. Reporting moved to \`prune: { unresolvedPath: 'warn' }\`, which \`'accounted'\` used to imply.` : ""}`);
+	}
 	for (const [name, pattern] of Object.entries(config.patterns ?? {})) {
 		const dictPattern = pattern;
 		if (!dictPattern) continue;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamboocss/config",
-  "version": "1.43.1",
+  "version": "1.44.0",
   "description": "Find and load bamboo config",
   "homepage": "https://bamboocss.com",
   "license": "MIT",
@@ -64,11 +64,11 @@
     "escalade": "3.2.0",
     "microdiff": "1.5.0",
     "typescript": "6.0.2",
-    "@bamboocss/logger": "1.43.1",
-    "@bamboocss/preset-bamboo": "1.43.1",
-    "@bamboocss/preset-base": "1.43.1",
-    "@bamboocss/shared": "1.43.1",
-    "@bamboocss/types": "1.43.1"
+    "@bamboocss/logger": "1.44.0",
+    "@bamboocss/preset-bamboo": "1.44.0",
+    "@bamboocss/preset-base": "1.44.0",
+    "@bamboocss/shared": "1.44.0",
+    "@bamboocss/types": "1.44.0"
   },
   "devDependencies": {
     "pkg-types": "2.3.0"