Reorder ESLint rules and improve test errors

Move ...strictRules after the TypeScript recommended rules in eslint.config.js so strictRules override the recommended settings. Improve htmlhint test failure diagnostics by capturing the caught error message (or 'Unknown error') and including the config path and message in assert.fail, making failures easier to debug.

Author: coliff

eslint.config.js

@@ -45,8 +45,8 @@ module.exports = [
       "@typescript-eslint": tseslint,
     },
     rules: {
-      ...strictRules,
       ...tseslint.configs.recommended.rules,
+      ...strictRules,
       "@typescript-eslint/explicit-module-boundary-types": "off",
       "@typescript-eslint/no-empty-interface": "off",
       "@typescript-eslint/no-explicit-any": "off",

test/suite/htmlhint.test.ts

@@ -33,17 +33,22 @@ suite("HTMLHint Test Suite", () => {
       );
       try {
         await vscode.workspace.fs.stat(vscode.Uri.file(testConfigPath));
-      } catch {
-        assert.fail(".htmlhintrc should exist in test config directory");
+      } catch (error) {
+        const message =
+          error instanceof Error ? error.message : "Unknown error";
+        assert.fail(
+          `.htmlhintrc should exist in test config directory: ${testConfigPath} (${message})`,
+        );
       }
       return;
     }
 
     const configPath = path.join(workspaceFolder.uri.fsPath, ".htmlhintrc");
     try {
       await vscode.workspace.fs.stat(vscode.Uri.file(configPath));
-    } catch {
-      assert.fail(".htmlhintrc should exist");
+    } catch (error) {
+      const message = error instanceof Error ? error.message : "Unknown error";
+      assert.fail(`.htmlhintrc should exist: ${configPath} (${message})`);
     }
   });
 });