@bamboocss/config 1.41.1 → 1.42.0

package/dist/diff-config.cjs

@@ -62,7 +62,7 @@ const format = [
 	"hash",
 	"prefix",
 	"separator",
-	"strictTokens",
+	"strictValues",
 	"strictPropertyValues",
 	"shorthands"
 ];

package/dist/diff-config.mjs

@@ -38,7 +38,7 @@ const format = [
 	"hash",
 	"prefix",
 	"separator",
-	"strictTokens",
+	"strictValues",
 	"strictPropertyValues",
 	"shorthands"
 ];

package/dist/index.cjs

@@ -143,7 +143,7 @@ const format = [
 	"hash",
 	"prefix",
 	"separator",
-	"strictTokens",
+	"strictValues",
 	"strictPropertyValues",
 	"shorthands"
 ];
@@ -1106,7 +1106,7 @@ const validateTokens = (options) => {
 //#region src/validate-config.ts
 /**
 * Validate the config
-* - Check that `strictTokens` names a setting that exists
+* - Check that `strictValues` names a setting that exists
 * - Check for duplicate between token & semanticTokens names
 * - Check for duplicate between recipes/patterns/slots names
 * - Check for token / semanticTokens paths (must end/contain 'value')
@@ -1137,7 +1137,7 @@ const validateConfig = (config) => {
 		return warnings;
 	};
 	if (config.validation === "off") return report();
-	validateStrictTokens(config.strictTokens, addError);
+	validateStrictValues(config.strictValues, addError);
 	validateBreakpoints(config.theme?.breakpoints, addError);
 	validateConditions(config.conditions, addError);
 	const artifacts = {
@@ -1170,16 +1170,16 @@ const validateConfig = (config) => {
 	return report();
 };
 /**
-* `strictTokens` has three settings, and a fourth spelling is not one of them.
+* `strictValues` is a boolean, and a string is not one.
 *
-* It reaches the generated types as a comparison against two known values, so anything else is
-* neither: `strictTokens: 'unknown'` emitted a *fourth* prop shape — csstype's keywords without
-* the escape hatch — that no setting asks for, silently. A typo in the middle mode's name is the
-* likely way to get there, and the symptom is type errors that match no documented behaviour.
+* It reaches the generated types as a truthiness test, so a string that is not a setting is
+* simply *on* — and being on means every raw CSS value in the project is a type error, from a
+* config that looked like it was asking for something else. `'unknown-tokens'` in particular
+* used to be a setting and now is not, so it is the likely way to arrive here.
 */
-const validateStrictTokens = (value, addError) => {
-	if (value === void 0 || value === true || value === false || value === "unknown-tokens") return;
-	addError("strictTokens", `\`${JSON.stringify(value)}\` is not a setting. Use \`true\` for tokens only, \`'unknown-tokens'\` to reject a value that is neither a token nor a css keyword, or omit it.`);
+const validateStrictValues = (value, addError) => {
+	if (value === void 0 || typeof value === "boolean") return;
+	addError("strictValues", `\`${JSON.stringify(value)}\` is not a setting. Use \`true\` to require every value to be a token, or omit it. A misspelled token is reported by the build — see \`unresolvedToken\` — and needs no setting.`);
 };
 //#endregion
 //#region src/resolve-config.ts

package/dist/index.d.cts

@@ -1753,6 +1753,7 @@ declare const defaultPresets: ({
           value: string;
         };
       };
+      zIndex: import("@bamboocss/types").Recursive<import("@bamboocss/types").Token<string | number>> | undefined;
     };
     mixins: import("@bamboocss/types").Mixins;
     containerSizes: {

package/dist/index.d.mts

@@ -1753,6 +1753,7 @@ declare const defaultPresets: ({
           value: string;
         };
       };
+      zIndex: import("@bamboocss/types").Recursive<import("@bamboocss/types").Token<string | number>> | undefined;
     };
     mixins: import("@bamboocss/types").Mixins;
     containerSizes: {

package/dist/index.mjs

@@ -115,7 +115,7 @@ const format = [
 	"hash",
 	"prefix",
 	"separator",
-	"strictTokens",
+	"strictValues",
 	"strictPropertyValues",
 	"shorthands"
 ];
@@ -1078,7 +1078,7 @@ const validateTokens = (options) => {
 //#region src/validate-config.ts
 /**
 * Validate the config
-* - Check that `strictTokens` names a setting that exists
+* - Check that `strictValues` names a setting that exists
 * - Check for duplicate between token & semanticTokens names
 * - Check for duplicate between recipes/patterns/slots names
 * - Check for token / semanticTokens paths (must end/contain 'value')
@@ -1109,7 +1109,7 @@ const validateConfig = (config) => {
 		return warnings;
 	};
 	if (config.validation === "off") return report();
-	validateStrictTokens(config.strictTokens, addError);
+	validateStrictValues(config.strictValues, addError);
 	validateBreakpoints(config.theme?.breakpoints, addError);
 	validateConditions(config.conditions, addError);
 	const artifacts = {
@@ -1142,16 +1142,16 @@ const validateConfig = (config) => {
 	return report();
 };
 /**
-* `strictTokens` has three settings, and a fourth spelling is not one of them.
+* `strictValues` is a boolean, and a string is not one.
 *
-* It reaches the generated types as a comparison against two known values, so anything else is
-* neither: `strictTokens: 'unknown'` emitted a *fourth* prop shape — csstype's keywords without
-* the escape hatch — that no setting asks for, silently. A typo in the middle mode's name is the
-* likely way to get there, and the symptom is type errors that match no documented behaviour.
+* It reaches the generated types as a truthiness test, so a string that is not a setting is
+* simply *on* — and being on means every raw CSS value in the project is a type error, from a
+* config that looked like it was asking for something else. `'unknown-tokens'` in particular
+* used to be a setting and now is not, so it is the likely way to arrive here.
 */
-const validateStrictTokens = (value, addError) => {
-	if (value === void 0 || value === true || value === false || value === "unknown-tokens") return;
-	addError("strictTokens", `\`${JSON.stringify(value)}\` is not a setting. Use \`true\` for tokens only, \`'unknown-tokens'\` to reject a value that is neither a token nor a css keyword, or omit it.`);
+const validateStrictValues = (value, addError) => {
+	if (value === void 0 || typeof value === "boolean") return;
+	addError("strictValues", `\`${JSON.stringify(value)}\` is not a setting. Use \`true\` to require every value to be a token, or omit it. A misspelled token is reported by the build — see \`unresolvedToken\` — and needs no setting.`);
 };
 //#endregion
 //#region src/resolve-config.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamboocss/config",
-  "version": "1.41.1",
+  "version": "1.42.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.41.1",
-    "@bamboocss/preset-bamboo": "1.41.1",
-    "@bamboocss/preset-base": "1.41.1",
-    "@bamboocss/shared": "1.41.1",
-    "@bamboocss/types": "1.41.1"
+    "@bamboocss/logger": "1.42.0",
+    "@bamboocss/preset-bamboo": "1.42.0",
+    "@bamboocss/preset-base": "1.42.0",
+    "@bamboocss/shared": "1.42.0",
+    "@bamboocss/types": "1.42.0"
   },
   "devDependencies": {
     "pkg-types": "2.3.0"