The functionality behind eslint --init has been pulled into a standalone @eslint/create-config package. Now, you can initialize ESLint in a new project with npm init @eslint/config, npx @eslint/create-config, or yarn create @eslint/config.
Several rules gained support for arbitrary module namespace names.
Features
19ad061 feat: no-restricted-imports support casing (#15439) (gfyoung)
564ecdb feat: Support arbitrary module namespace names in no-restricted-imports (#15491) (Milos Djermanovic)
968a02a feat: Support arbitrary module namespace names in no-useless-rename (#15493) (Milos Djermanovic)
0d2b9a6 feat: move eslint --init to @eslint/create-config (#15150) (唯然)
127f524 feat: false negative with property option in id-match (#15474) (Nitin Kumar)
359b2c1 feat: Support arbitrary module namespace names in the camelcase rule (#15490) (Milos Djermanovic)
3549571 feat: Support arbitrary module namespace names in the quotes rule (#15479) (Milos Djermanovic)
5563c45 feat: Support arbitrary module namespace names in keyword-spacing (#15481) (Milos Djermanovic)
fd3683f feat: Support arbitrary module namespace names in no-restricted-exports (#15478) (Milos Djermanovic)
Bug Fixes
a8db9a5 fix: no-invalid-this false positive in class field initializer (#15495) (Milos Djermanovic)