Tony Ganchev comments

Results 13 comments of


                                            Tony Ganchev

High CPU usage and memory consumption even if doing nothing

Similar problems. on leaving my WSL dormant for the night I find it in the morning with 100% memory usage (24 GiB) and 40+ RedHat java agents running.

BREAKING CHANGE: Moving to latest version of `@typescript-eslint/utils`

One more upvote. We're completely blocked on our eslint 9 migration because of this.

Add support to set a year or year range dynamically from the year range extracts from the previous header

I forked https://github.com/tonyganchev/eslint-plugin-header/ and publish new versions and would love to review the change.

fix: disable rule options schema validation in eslint 9, fix https://github.com/Stuk/eslint-plugin-header/issues/57

I've published a fork at https://www.npmjs.com/package/@tony.ganchev/eslint-plugin-header containing my fix.

Error: Key "rules": Key "header/header": should NOT have more than 0 items.

Also reproducing this issue.

Error: Key "rules": Key "header/header": should NOT have more than 0 items.

Seems that ESLint now mandates that meta.schema field is mandatory for rules with options: https://eslint.org/docs/latest/extend/custom-rules. I went ahead and set `schema: false` before https://github.com/Stuk/eslint-plugin-header/blob/63f18ce725edb23a2d274b234df7f12ff0b7f009/lib/rules/header.js#L125 and linting passed. I can probably...

False positives when meta contains spread with `prefer-message-ids`, `require-meta-type`, `require-meta-fixable`, `require-meta-schema`

I have similar issues with `eslint-plugin/require-meta-docs-*` rules. Basicually if I move the `docs` definition out of the `meta` JSON, I cannot get any of the rules to pass e.g. both...