Add theme-utils

README.md

@@ -199,6 +199,9 @@ You can then use the following commands to test the code:
 - **`npm run lint:css:fix`**: Lints and attempts to autofix any issues in the CSS files.
 - **`npm run lint:php`**: Checks PHP files for syntax and standards errors according to [WordPress coding standards](https://developer.wordpress.org/coding-standards/).
 - **`npm run lint:php:fix`**: Attempts to automatically fix PHP errors.
+- **`lint:theme`**: Checks the theme.json and style.css metadata for issues.
+- **`lint:patterns:fix`**: Attempts to automatically wrap text in patterns for translation. Please check the updated files after running for adding additional context that may be needed or text that the tool wasn't able to automatically wrap.
+
 
 ## Resources
 

package.json

@@ -23,12 +23,22 @@
 	},
 	"devDependencies": {
 		"@wordpress/stylelint-config": "^22.5.0",
-		"stylelint": "^14.16.1"
+		"ajv": "^8.17.1",
+		"ajv-draft-04": "^1.0.0",
+		"chalk": "^5.3.0",
+		"fast-glob": "^3.3.2",
+		"parse5-html-rewriting-stream": "^7.0.0",
+		"semver": "^7.6.3",
+		"string-progressbar": "^1.0.4",
+		"stylelint": "^14.16.1",
+		"table": "^6.8.2"
 	},
 	"scripts": {
 		"lint:css": "stylelint **/*.css -i .gitignore",
 		"lint:css:fix": "stylelint **/*.css -i .gitignore --fix",
 		"lint:php": "composer run-script lint",
-		"lint:php:fix": "composer run-script format"
+		"lint:php:fix": "composer run-script format",
+		"lint:theme": "node theme-utils.mjs validate-theme",
+		"lint:patterns:fix": "node theme-utils.mjs escape-patterns --text-domain=twentytwentyfive"
 	}
 }