Shahar "Dawn" Or

Thanks for all the effort! I'm confused. There are two repositories: - magic-nix-cache-action - magic-nix-cache And there's flakehub-cache-action as well. 🤷 help?

Thank you for the exaplanation. I wish the readmes made all this clear and did not instruct to use an unrelated flakehub-cache-action.

I think we can't do this yet. Must wait until all the plugins support it.

This seems to be waiting for: - [ ] https://github.com/import-js/eslint-plugin-import/issues/2948 - [x] https://github.com/eslint-community/eslint-plugin-promise/issues/449 - [x] typescript-eslint v8

I'd love some user input on this. Are you applying this to JS files, as well as TS files? Is that practical?

https://github.com/mightyiam/eslint-config-love/actions/runs/9249126614/job/25440475210#step:5:5 ``` npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: '@semantic-release/[email protected]', npm warn EBADENGINE required: { node: '>=20.8.1' }, npm warn EBADENGINE current: { node: 'v18.20.2', npm: '10.8.0'...

Waiting for all plugins to support it.

Two things need to happen: 1. #1699 (possibly this weekend) 2. one of 1. https://github.com/import-js/eslint-plugin-import/issues/2948 2. migrating to a fork of the above

Now that we have typescript-eslint v8, the remaining blocker is [eslint-plugin-import](https://github.com/import-js/eslint-plugin-import/issues/2948). And I'm not sure what to do about that except for waiting. The fork could work, but I feel...

https://github.com/eslint/rewrite/tree/9250f2842456dff373508dce50cff536e32d8686/packages/compat usage seems trivial. I wonder though how do we know that all fixed rules still work...