@zthun/janitor-lint 19.5.2 → 19.5.3

package/README.md

@@ -1,29 +1,29 @@
 # Janitor Lint
 
-Code gets messy. Most places you work will have a long backlog of tech-debt tasks
-that never quite get addressed, and over time this becomes a maintenance nightmare.
-Fixing old problems is expensive, and companies tend to focus on short-term ROI —
-which means these issues often stay unresolved. New features get built on top of
-messy foundations, and the software slowly begins to rot.
+Code gets messy. Most places you work will have a long backlog of tech-debt
+tasks that never quite get addressed, and over time this becomes a maintenance
+nightmare. Fixing old problems is expensive, and companies tend to focus on
+short-term ROI — which means these issues often stay unresolved. New features
+get built on top of messy foundations, and the software slowly begins to rot.
 
 A common way to fight this is to start with linters. Linters scan your codebase
-and notify you of issues. In a healthy development pipeline, they prevent developers
-from creating a metaphorical messy room and encourage clean, consistent code across
-the team. They’re not a silver bullet — messy solutions can still appear — but
-linters eliminate most inconsistent patterns and formatting errors. Good developers
-love them because they keep everyone aligned.
+and notify you of issues. In a healthy development pipeline, they prevent
+developers from creating a metaphorical messy room and encourage clean,
+consistent code across the team. They’re not a silver bullet — messy solutions
+can still appear — but linters eliminate most inconsistent patterns and
+formatting errors. Good developers love them because they keep everyone aligned.
 
 However, linters come with their own problems. There are so many of them. Each
 has its own configuration style, quirks, and ecosystem. To cover your full
-codebase, you often need multiple tools: ones for code quality, formatting, spelling,
-applications, and more. It’s easy to feel overwhelmed, and maintaining a stack of
-linters becomes its own form of tech debt.
+codebase, you often need multiple tools: ones for code quality, formatting,
+spelling, applications, and more. It’s easy to feel overwhelmed, and maintaining
+a stack of linters becomes its own form of tech debt.
 
 Janitor Lint was created with the belief that there is beauty in simplicity. A
-single tool that handles your linting needs is far better than stitching together
-a pile of utilities, each with its own configuration and upkeep. Let Janitor
-Lint take on the heavy lifting so you can keep your codebase clean — and your
-developers happy.
+single tool that handles your linting needs is far better than stitching
+together a pile of utilities, each with its own configuration and upkeep. Let
+Janitor Lint take on the heavy lifting so you can keep your codebase clean — and
+your developers happy.
 
 ## Install
 
@@ -39,17 +39,17 @@ yarn add -D @zthun/janitor-lint-config
 janitor-lint
 ```
 
-- `--config` is optional. Without it, the CLI searches for a `janitor`
-  config using cosmiconfig (in order: `package.json#janitor`, `janitorrc`,
+- `--config` is optional. Without it, the CLI searches for a `janitor` config
+  using cosmiconfig (in order: `package.json#janitor`, `janitorrc`,
   `janitorrc.json`, `janitorrc.yaml|yml`, `janitorrc.mjs`).
 - Exit code is `0` when every enabled linter passes and `1` when any fail.
 
 ## Configuration shape
 
-Janitor Lint reads a `janitor` options config object with a `lint` section. Every
-field is optional—only the linters you configure will run. You can configure this
-manually, OR you can use the package, @zthun/janitor-options, to just build a
-configuration.
+Janitor Lint reads a `janitor` options config object with a `lint` section.
+Every field is optional—only the linters you configure will run. You can
+configure this manually, OR you can use the package, @zthun/janitor-options, to
+just build a configuration.
 
 ```ts
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zthun/janitor-lint",
-  "version": "19.5.2",
+  "version": "19.5.3",
   "description": "Style checks with tools for web projects using common rules.",
   "keywords": [
     "linters"
@@ -33,29 +33,29 @@
   },
   "author": "Anthony Bonta",
   "dependencies": {
-    "@zthun/janitor-options": "^19.5.2",
+    "@zthun/janitor-options": "^19.5.3",
     "chalk": "^5.6.2",
     "cosmiconfig": "^9.0.0",
-    "cspell": "^9.3.2",
-    "eslint": "^9.39.1",
+    "cspell": "^9.4.0",
+    "eslint": "^9.39.2",
     "glob": "^13.0.0",
-    "htmlhint": "^1.7.1",
+    "htmlhint": "^1.8.0",
     "js-yaml": "^4.1.1",
     "lodash-es": "^4.17.21",
-    "markdownlint": "~0.39.0",
-    "prettier": "^3.6.2",
-    "stylelint": "^16.26.0",
+    "markdownlint": "~0.40.0",
+    "prettier": "^3.7.4",
+    "stylelint": "^16.26.1",
     "yargs": "^18.0.0"
   },
   "files": [
     "dist"
   ],
   "devDependencies": {
-    "@zthun/janitor-build-config": "^19.5.2",
+    "@zthun/janitor-build-config": "^19.5.3",
     "typescript": "~5.9.3",
-    "vite": "^7.2.4",
-    "vitest": "^4.0.13",
+    "vite": "^7.2.7",
+    "vitest": "^4.0.15",
     "vitest-mock-extended": "^3.1.0"
   },
-  "gitHead": "bca82c3034dae1ea5c347075f6c46376b50c1660"
+  "gitHead": "0346801ebb985f75ab3d5faeb8677e6c6a14d9b2"
 }