feature/design-tokens-module

.eslintrc.js

@@ -18,6 +18,7 @@ const eslintConfig = {
 		history: 'readonly',
 		location: 'readonly',
 		IntersectionObserver: 'readonly',
+		ResizeObserver: 'readonly',
 		kadenceFormAnalyticsParams: 'readonly',
 		Element: 'readonly',
 		kadence_blocks_params_fa: 'readonly',
@@ -132,6 +133,12 @@ const eslintConfig = {
 		'jsdoc/check-alignment': 'off',
 	},
 	ignorePatterns: [],
+	overrides: [
+		{
+			files: [ '**/__tests__/**/*.js', '**/*.test.js' ],
+			extends: [ 'plugin:@wordpress/eslint-plugin/test-unit' ],
+		},
+	],
 };
 
 module.exports = eslintConfig;

jest-unit.config.js

@@ -0,0 +1,24 @@
+/**
+ * Jest configuration for the package's unit tests.
+ *
+ * Built from `@wordpress/jest-preset-default`'s own settings (JSX babel transform, scss mocking,
+ * jsdom environment, testMatch) rather than via Jest's `preset` field: Jest MERGES (concatenates)
+ * array-valued options like `setupFilesAfterEnv` between a preset and the local config, so setting
+ * `preset` directly would keep `@wordpress/jest-console`'s strict fail-on-console-warning behavior
+ * even after this file lists its own `setupFilesAfterEnv`. This package's control tests render
+ * against a newer test-only `@wordpress/components` devDependency than the one the consuming app
+ * (e.g. kadence-blocks) actually provides at runtime, which emits deprecation warnings unrelated to
+ * the behavior under test — so that strict policing does not apply here.
+ */
+const wpJestPreset = require('@wordpress/jest-preset-default/jest-preset.js');
+
+module.exports = {
+	...wpJestPreset,
+	setupFilesAfterEnv: ['<rootDir>/test/config/jest.setup.js'],
+	moduleNameMapper: {
+		...wpJestPreset.moduleNameMapper,
+		'^@kadence/icons$': '<rootDir>/test/mocks/kadence-icons.js',
+		'^@kadence/helpers$': '<rootDir>/test/mocks/kadence-helpers.js',
+	},
+	testPathIgnorePatterns: [...(wpJestPreset.testPathIgnorePatterns || []), '<rootDir>/dist/'],
+};