@zthun/janitor-eslint-config 20.0.1 → 20.0.3

package/lib/configs/html.mjs

@@ -13,8 +13,13 @@ export const html = defineConfig([
   {
     files: files(...ExtHtml),
     rules: {
-      // Prettier defaults to 2 spaces, so this needs to as well.
-      "@html-eslint/indent": ["error", 2],
+      // All of these rules conflict with prettier and that linter
+      // is the highest priority for formatting.  So we don't need
+      // these rules turned on.
+      "@html-eslint/indent": "off",
+      "@html-eslint/no-extra-spacing-attrs": "off",
+      "@html-eslint/require-closing-tags": "off",
+      "@html-eslint/attrs-newline": "off",
     },
   },
   {

package/lib/configs/ignores.mjs

@@ -12,5 +12,6 @@ export const ignores = defineConfig([
     "**/.yarn",
     "**/*.husky",
     "**/lerna.json",
+    "**/cspell.json",
   ]),
 ]);

package/lib/configs/typescript.mjs

@@ -49,9 +49,21 @@ export const typescript = defineConfig([
       // be required to use any at some point.  Forcing a non use of them
       // means you're spending a bunch of time play type gymnastics and to
       // hell with that.
-      "@typescript-eslint/no-explicit-any": "off",
       "@typescript-eslint/no-namespace": "off",
 
+      // JavaScript is any by default; The sentiment here is understood
+      // to prefer unknown over any but there are times where any
+      // helps, especially if we don't have a typescript api for
+      // a 3rd party dependency.  If something is declared as any,
+      // let's treat it as it is meant to be used.  May revisit this
+      // decision later on, but for now, any is allowed.
+      "@typescript-eslint/no-explicit-any": "off",
+      "@typescript-eslint/no-unsafe-assignment": "off",
+      "@typescript-eslint/no-unsafe-argument": "off",
+      "@typescript-eslint/no-unsafe-call": "off",
+      "@typescript-eslint/no-unsafe-member-access": "off",
+      "@typescript-eslint/no-unsafe-return": "off",
+
       // Would be fine, but there's a bug in this where you have a function with
       // access arguments.  Those constructors are often empty - so we want to let
       // a part of this one through.
@@ -70,6 +82,11 @@ export const typescript = defineConfig([
       "@typescript-eslint/no-empty-object-type": "off",
       "@typescript-eslint/no-empty-interface": "off",
 
+      // This rule conflicts with development styles like react which use hooks and
+      // often want to pass methods around without the assumption that it is attached
+      // to a this pointer.
+      "@typescript-eslint/unbound-method": "off",
+
       // You will need unsafe declaration merging if you are doing anything
       // with decorators as what often happens is that TypeScript cannot infer
       // the output type of a decorator. So this has to be on to deal with

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zthun/janitor-eslint-config",
-  "version": "20.0.1",
+  "version": "20.0.3",
   "description": "A shared configuration for eslint for @zthun scoped projects.",
   "keywords": [
     "eslint",
@@ -42,7 +42,7 @@
     "typescript-eslint": "^8.58.0"
   },
   "devDependencies": {
-    "@zthun/janitor-build-config": "^20.0.0",
+    "@zthun/janitor-build-config": "^20.0.2",
     "eslint": "^9.39.4",
     "prettier": "^3.8.1",
     "typescript": "~5.9.3",
@@ -63,5 +63,5 @@
     "access": "public"
   },
   "author": "Anthony Bonta",
-  "gitHead": "2751f2fb1ee4a12298c1125281a6c27e922e3262"
+  "gitHead": "10c75a160057497eca34185883ae35753c0bc763"
 }