Skip to content

chore: switch to @tony.ganchev/eslint-plugin-header#27663

Open
tonyganchev wants to merge 1 commit intomicrosoft:mainfrom
tonyganchev:main
Open

chore: switch to @tony.ganchev/eslint-plugin-header#27663
tonyganchev wants to merge 1 commit intomicrosoft:mainfrom
tonyganchev:main

Conversation

@tonyganchev
Copy link

@tonyganchev tonyganchev commented Mar 15, 2026

Hi, team,

I noticed you are using eslint-plugin-header with the schema-turn-off
workaround to support ESLint 9.

I forked @tony.ganchev/eslint-plugin-header mid-2024 to address this
issue and hoped it would be a temporary measure but since the original has
not been updated for five years I decided to continue improving the new
plugin. Specific improvements include:

  • full JSON schema for validating the configuration.
  • fixed multiple bugs with the behavior of the plugin on Windows.
  • improved autofixing and error-reporting behavior.
  • added support for leading pragma comments before the header such as
    @jest-environment.

This fork is already widely used by other Microsoft projects especially
in the VSCode plugin ecosystem (and I have sent a similar PR proposal
to the core VSCode maintainers).

Looking forward to your feedback.

Signed-off-by: Tony Ganchev tony.ganchev@gmail.com

Hi, team,

I noticed you are using _eslint-plugin-header_ with the schema-turn-off
workaround to support ESLint 9.

I forked _@tony.ganchev/eslint-plugin-header_ mid-2024 to address this
issue hoped it would be a temporary measure but since the original has
not been updated for five years I decided to continue improving the new
plugin. Specific improvements include:
- full JSON schema for validating the configuration.
- fixed multiple bugs with the behavior of the plugin on Windows.
- improved autofixing and error-reporting behavior.
- added support for leading pragma comments before the header such as
  `@jest-environment`.

This fork is already widely used by other Microsoft projects especially
in the VSCode plugin ecosystem (and I have sent a similat PR proposal
to the core VSCode maintainers).

Looking forward for your feedback.

Signed-off-by: Tony Ganchev <tony.ganchev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant