Docs(eslint-config-typescript): Update readme according the new flat config support

Author: literat

packages/eslint-config-typescript/README.md

@@ -1,59 +1,50 @@
 # @alma-oss/eslint-config-typescript
 
-These configuration files are suitable to lint TypeScript code.
+> ESLint configuration for TypeScript projects
 
-## Setup
+## 📦 Installation
 
-To lint TypeScript files using ESLint and this ruleset you must
-
-1. Install ESLint & this ruleset
-1. Tell the TypeScript parser where your _tsconfig.json_ file is (not doing so will cause some TS-syntax-specific rules to not work at all)
-1. Extend one or more of the included rulesets
-
-See the example _.eslintrc.js_ file below for more details and make sure you read the [Parser’s docs][ts-parser-configuration] about its settings.
+```sh
+npm install --save-dev eslint @alma-oss/eslint-config-typescript
+# or
+yarn add --dev eslint @alma-oss/eslint-config-typescript
+```
 
-## Configurations
+## 🧩 Rulesets
 
 - **`@alma-oss/eslint-config-typescript`**
 
-Suitable for linting TypeScript source files.
-
-Together with this ruleset, you should also choose one base ruleset depending on your target platform:
+A generic ruleset that focuses on code correctness.
 
-- [`@alma-oss/eslint-config-node`][eslint-config-node]
-- [`@alma-oss/eslint-config-react`][eslint-config-react]
+- **`@alma-oss/eslint-config-typescript/optional`**
 
-### `@alma-oss/eslint-config-typescript/react`
+Additional ruleset that might provide useful tips and hints how to improve your code.
 
-React specific overrides.
-
-## Optional Configurations
-
-### `@alma-oss/eslint-config-typescript/optional`
+> For new projects, it is recommended to enable this ruleset. For existing projects, it is only recommended for the brave.
 
-Use this ruleset together with any of the above version-specific rulesets. Provides additional insights into potential inconsistencies in the project.
+- **`@alma-oss/eslint-config-typescript/style`**
 
-> For new projects, it is recommended to enable this ruleset. For existing projects, it is only recommended for the brave.
+Ruleset that focuses on code style (indentation, spacing, naming, syntax preference etc.).
 
-## Coding Styles
+- **`@alma-oss/eslint-config-typescript/react`**
 
-### `@alma-oss/eslint-config-typescript/style`
+Ruleset that provides additional customizations for the `@alma-oss/eslint-config-react` ruleset when working with TypeScript.
 
-This ruleset includes rules which deal with how the code looks like and not how it works. It helps keeping the code clean and consistent. 🎨
+## 👨‍💻 Usage
 
 A full configuration for a TypeScript on Node.js project:
 
 ```js
 // eslint.config.js
-import { defineConfig } from 'eslint/config';
+import typescript from '@alma-oss/eslint-config-typescript';
+import optional from '@alma-oss/eslint-config-typescript/optional';
+import style from '@alma-oss/eslint-config-typescript/style';
 
+/** @type {Array<import("eslint").Linter.Config>} */
 export default defineConfig({
-  extends: [
-    '@alma-oss/eslint-config-node/v10',
-    '@alma-oss/eslint-config-node/optional',
-    '@alma-oss/eslint-config-typescript',
-    '@alma-oss/eslint-config-typescript/style',
-  ],
+  ...typescript,
+  ...optional,
+  ...style,
 
   parserOptions: {
     // The project field is required in order for some TS-syntax-specific rules to function at all
@@ -70,21 +61,17 @@ A full configuration for a TypeScript on React project:
 ```js
 // eslint.config.mjs
 import { defineConfig, globalIgnores } from 'eslint/config';
-import { FlatCompat } from '@eslint/eslintrc';
-import react from '@alma-oss/eslint-config-react';
-import reactOptional from '@alma-oss/eslint-config-react/optional';
-import ts from '@alma-oss/eslint-config-typescript';
-import tsReact from '@alma-oss/eslint-config-typescript/react';
-
-const compat = new FlatCompat({
-  baseDirectory: import.meta.dirname,
-});
+import typescript from '@alma-oss/eslint-config-typescript';
+import react from '@alma-oss/eslint-config-typescript/react';
+import optional from '@alma-oss/eslint-config-typescript/optional';
+import style from '@alma-oss/eslint-config-typescript/style';
 
 export default defineConfig([
+  ...typescript,
   ...react,
-  ...reactOptional,
-  ...ts,
-  ...tsReact,
+  ...optional,
+  ...style,
+
   {
     parserOptions: {
       // The project field is required in order for some TS-syntax-specific rules to function at all
@@ -95,13 +82,9 @@ export default defineConfig([
 ]);
 ```
 
-To actually lint .ts files, you must pass the `--ext` flag to ESLint:
-
-```sh
-eslint --ext ts --report-unused-disable-directives .
-```
+## 🔌 Integration
 
-## VSCode integration
+### Visual Studio Code
 
 The [vscode-eslint](https://github.com/Microsoft/vscode-eslint) plugin for integrating ESLint into VSCode does not automatically parse TypeScript files. To do so, you must inform ESLint to enable on TypeScript files by adding this configuration to your settings (File > Preferences > Settings):
 
@@ -116,6 +99,16 @@ The [vscode-eslint](https://github.com/Microsoft/vscode-eslint) plugin for integ
 
 > Notice we are adding `javascriptreact` and `typescriptreact` above. It won’t harm adding those, but you can always omit these languages if not using them.
 
-[eslint-config-node]: https://www.npmjs.com/package/@alma-oss/eslint-config-node
+## 🙌 Contributing
+
+We’re always looking for contributors to help us fix bugs, build new features,
+or help us improve the project documentation. If you’re interested, definitely
+check out our [Contributing Guide][contributing]! 👀
+
+## 📝 License
+
+Licensed under the [MIT][license].
+
 [eslint-config-react]: https://www.npmjs.com/package/@alma-oss/eslint-config-react
-[ts-parser-configuration]: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/parser#configuration
+[contributing]: https://github.com/lmc-eu/code-quality-tools/blob/main/CONTRIBUTING.md
+[license]: https://github.com/lmc-eu/code-quality-tools/blob/main/LICENSE.md