Conversation
As required by ESLint 9: see https://eslint.org/blog/2024/04/eslint-v9.0.0-released/#changes-to-how-you-write-rules
Had to downgrade ESLint to v8 since the plugin is not compatible with ESLint9 (yet?) Stuk/eslint-plugin-header#56 Change-Id: I85a07ce19f1a8c30ff65f2c010edea81bc9366f0
|
@joshkel I have published the previous incremental fix to unblock work with ESLint9 - see #58. As I didn't get an approval on the PR, I had to publish from my fork: https://www.npmjs.com/package/@tony.ganchev/eslint-plugin-header. Would you mind creating a PR for this fork until the owners of the original repo fix the CI/CD (if I understand the status of this PR correctly...) |
Original PR: Stuk#56 As required by ESLint 9: see https://eslint.org/blog/2024/04/eslint-v9.0.0-released/#changes-to-how-you-write-rules
Original PR: Stuk#56 As required by ESLint 9: see https://eslint.org/blog/2024/04/eslint-v9.0.0-released/#changes-to-how-you-write-rules
Hey, @tonyganchev. Thanks for creating that fork. I apologize for not following up sooner. If I understand correctly, it looks like you already took care of this? |
That's right. Thanks, and pardon me for not waiting for the response :) |
3 participants
ESLint 9 now requires that plugins provide a schema if they accept options; see https://eslint.org/blog/2024/04/eslint-v9.0.0-released/#changes-to-how-you-write-rules.