@tony.ganchev/eslint-plugin-header 3.3.1 → 3.3.3

package/README.md

@@ -58,12 +58,16 @@ dedicated section.
 
 ## Compatibility
 
-The plugin supports ESLint 7 / 8 / 9 / 10. Both flat config and legacy,
-hierarchical config can be used.
+The plugin supports **ESLint 7 / 8 / 9 / 10**. Both **flat** config and legacy,
+**hierarchical** config can be used. We have a smoke-test running to confirm the
+plugin works with the latest version of ESLint.
+
+The plugin works with latest version of **oxlint** too. We have a smoke-test
+running to confirm the plugin works with the latest version of oxlint.
 
 The NPM package provides TypeScript type definitions and can be used with
 TypeScript-based ESLint flat configuration without the need for `@ts-ignore`
-statements.
+statements. Smoke tests cover this support as well.
 
 ## Usage
 

package/lib/rules/header.js

@@ -898,15 +898,6 @@ const headerRule = {
         },
         fixable: "whitespace",
         schema,
-        defaultOptions: [
-            /** @type {AllHeaderOptions} */
-            {
-                lineEndings: lineEndingOptions.os,
-                trailingEmptyLines: {
-                    minimum: 1
-                }
-            }
-        ],
         messages: {
             // messages customized for header validation.
             headerLineMismatchAtPos:
@@ -973,11 +964,20 @@ const headerRule = {
             Program: function () {
                 const sourceCode = contextSourceCode(context);
                 const leadingComments = getLeadingComments(sourceCode);
-                const hasShebang = leadingComments.length > 0
-                    && /** @type {string} */ (leadingComments[0][0].type) === "Shebang";
+                // XXX: the reason we test like this instead of checking the
+                // first comment is of type "Shabeng" is because
+                // @typecript-eslint/prser does not recognize shebang comments
+                // with some TypeScript configuration. Since we are not
+                // releasing a major version we do not want to break the current
+                // behavior of not be pedantic about the tsconfig.json.
+                const hasShebang = sourceCode.text.startsWith("#!");
                 let startingHeaderLine = 1;
                 if (hasShebang) {
-                    leadingComments.splice(0, 1);
+                    if (leadingComments.length > 0
+                        && /** @type {string} */ (leadingComments[0][0].type) === "Shebang"
+                    ) {
+                        leadingComments.splice(0, 1);
+                    }
                     startingHeaderLine = 2;
                 }
 

package/lib/rules/header.schema.js

@@ -98,7 +98,7 @@ const schema = Object.freeze({
             type: "string",
             enum: [lineEndingOptions.unix, lineEndingOptions.windows, lineEndingOptions.os],
             description: "Line endings to use when aut-fixing the violations. Defaults to 'os' which means 'same as " +
-            "system'."
+                "system'."
         },
         settings: {
             type: "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tony.ganchev/eslint-plugin-header",
-  "version": "3.3.1",
+  "version": "3.3.3",
   "description": "The native ESLint 9/10 header plugin. A zero-bloat, drop-in replacement for 'eslint-plugin-header' with first-class Flat Config & TypeScript support. Auto-fix Copyright, License, and banner comments in JavaScrip and TypeScript files.",
   "main": "index.js",
   "types": "index.d.ts",
@@ -35,7 +35,7 @@
     "mocha": "12.0.0-beta-10",
     "testdouble": "^3.20.2",
     "typescript": "^5.9.3",
-    "typescript-eslint": "^8.57.0"
+    "typescript-eslint": "^8.57.1"
   },
   "peerDependencies": {
     "eslint": ">=7.7.0"