I'm considering archiving this package

[ota-meshi]

I haven't used this package for a long time, so I don't want to spend any more time maintaining it.

If you want this package to continue to be maintained, can you please write your ideas for how to continue maintaining it?

[yusufkandemir]

We are using this package on https://github.com/quasarframework/quasar/tree/dev/create-quasar and I am very happy with it. Thanks for the amazing work!

I was migrating the monorepo to ESLint v9 + flat config, and noticed settings(e.g. lodash-template/globals) do not work. I checked the config loading logic of this library, and it does a lot of hackery to get the config due to version ESLint version differences. And it doesn't expect the config to be an array, so it fails. I think it must use config for the file it's going to process. Anyway, I think the main point here is that supporting many ESLint versions complicates things a lot.
I would suggest releasing a new major version that only supports ESLint v9 to greatly simplify the internals and prepare for future updates. I think the plugin is in a good/acceptable state in terms of features and stability. So, updating this package only for version upgrades should be enough after that point, which should hopefully be very rarely required.

[ota-meshi]

We are using this package on https://github.com/quasarframework/quasar/tree/dev/create-quasar and I am very happy with it. Thanks for the amazing work!

I'm glad to hear that.

However, I don't understand what you're proposing regarding the continued maintenance of this package.
Would you open a new issue if you want to report a bug?
Or are you just saying that you're interested in maintaining this package?

[yusufkandemir]

Sorry for the late response! I wasn’t just reporting a bug. That bug is likely a result of having to support multiple ESLint versions, and I wanted to point that out. I suggested releasing a new major version that only supports ESLint v9 and later, which would simplify the internals and make future updates easier to manage.

I believe this change would make things more stable and less complex in the long run, given that supporting multiple versions of ESLint is becoming increasingly difficult. I've created #388 for this.

I don't have much domain knowledge and time. So, unfortunately, I won't be able to maintain this project. But, I created the PR, which should hopefully reduce the maintenance burden, make it easier to contribute to this package, and future-proof the package.

[ota-meshi]

Thanks for the PR 😄
But unless someone is willing to take over maintenance, I don't intend to make any major changes (and breaking changes) to this package, as it would increase the maintenance load temporarily, and I don't have the time to do that.