@moso/eslint-config 1.0.4 → 2.0.2

package/README.md

@@ -4,28 +4,230 @@
 
 Flat ESLint config for JavaScript, TypeScript, Vue, React, and more.
 
-[Legacy Version](https://github.com/moso/eslint-config/tree/legacy).
-
 ## Features
 
 - [ESLint Flat config](https://eslint.org/docs/latest/use/configure/configuration-files-new) with reasonable but opinionated defaults
-- Single quotes, semi enabled, sorted imports, dangling commas,
+- [Stylistic](https://eslint.style) with single quotes, semi enabled, sorted imports, dangling commas,
 - Aimed to be used without Prettier
 - Designed to work with JSX, TypeScript, Vue, and React out of the box
-- [Stylistic](https://eslint.style) rules implemented by default
-- Lints for json and yaml
+- Applies [Functional](https://github.com/eslint-functional/eslint-plugin-functional) and [Perfectionist](https://perfectionist.dev) by default
+- Lints for JSDoc, JSON, RegEx, and YAML
+- Every config can be enabled/disabled
 - Respects `.gitignore` by default
-- Requires ESLint v9.5.0+
-
-> [!NOTE]
-> Since v1.0.0, this config is rewritten for the new [ESLint Flat config](https://eslint.org/docs/latest/use/configure/configuration-files-new) format.
->
-> ESLint v9.5.0+ is now required.
+- Requires ESLint v9.10.0+
+
+## Configs
+
+This section contains a list of the plugins used in the named configs that ships with this shareable config.
+
+\- ✅ Enabled by default  
+\- ☑️ Enabled by auto-detect  
+\- 🌟 Enabled unless `lessOpinionated: false`  
+\- 🟨 Can be enabled manually  
+\- 🎨 Stylistic rules enabled  
+\- 💭 Type-aware rules available by setting the path to your `tsconfig.json`  
+\- ℹ️ Accessibility rules available with `a11y: true`
+
+<table>
+<thead>
+<tr>
+<th align="left" width="1200" style="max-width: 100%">Plugin</th>
+<th>💼</th>
+<th>🎨</th>
+<th>💭</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>
+<details><summary><strong>ESLint Comments</strong></summary>
+
+[`eslint-plugin-eslint-comments`](https://eslint-community.github.io/eslint-plugin-eslint-comments)
 
-> [!WARNING]
-> While I'm very appreciative with every single install of this config, please keep in mind that this config is still a **personal**, opinionated config. How I like things set up might not fit everyone, or every usecase.
->
-> If you're using this config directly, I suggest you review the changes with every update. Or if you want more control over the very core of this config, feel free to fork it. Thanks!
+</details>
+</td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Functional</strong></summary>
+
+[`eslint-plugin-functional`](https://github.com/eslint-functional/eslint-plugin-functional)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Import Lite</strong></summary>
+
+[`eslint-plugin-import-lite`](https://github.com/9romise/eslint-plugin-import-lite)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>JavaScript</strong></summary>
+
+[`@eslint/js`](https://eslint.org), [`eslint-plugin-de-morgan`](https://github.com/azat-io/eslint-plugin-de-morgan), [`eslint-plugin-unused-imports`](https://github.com/sweepline/eslint-plugin-unused-imports)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>JSDoc</strong></summary>
+
+[`eslint-plugin-jsdoc`](https://github.com/gajus/eslint-plugin-jsdoc)
+
+</details></td>
+<td valign="top">🟨</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>JSONC</strong></summary>
+
+[`eslint-plugin-jsonc`](https://ota-meshi.github.io/eslint-plugin-jsonc)
+
+</details></td>
+<td valign="top">🟨</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Node</strong></summary>
+
+[`eslint-plugin-n`](https://github.com/eslint-community/eslint-plugin-n)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Perfectionist</strong></summary>
+
+[`eslint-plugin-perfectionist`](https://perfectionist.dev)
+
+</details></td>
+<td valign="top">🌟</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Promises</strong></summary>
+
+[`eslint-plugin-promise`](https://github.com/eslint-community/eslint-plugin-promise)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>React</strong></summary>
+
+[`@eslint-react`](https://eslint-react.xyz), [`@eslint-react/dom`](https://eslint-react.xyz), [`@eslint-react/hooks-extra`](https://eslint-react.xyz), [`@eslint-react/naming-convention`](https://eslint-react.xyz), [`@eslint-react/web-api`](https://eslint-react.xyz), [`eslint-plugin-react-hooks`](https://www.npmjs.com/package/eslint-plugin-react-hooks), [`eslint-plugin-react-you-might-not-need-an-effect`](https://github.com/NickvanDyke/eslint-plugin-react-you-might-not-need-an-effect), [`eslint-plugin-jsx-a11y`](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y)
+
+</details></td>
+<td valign="top">☑️ℹ️</td>
+<td valign="top">🎨</td>
+<td valign="top">💭</td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>RegExp</strong></summary>
+
+[`eslint-plugin-regexp`](https://ota-meshi.github.io/eslint-plugin-regexp)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Stylistic</strong></summary>
+
+[`@stylistic/eslint-plugin`](https://eslint.style)
+
+</details></td>
+<td valign="top">🌟</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Test</strong></summary>
+
+[`@vitest/eslint-plugin`](https://github.com/vitest-dev/eslint-plugin-vitest), [`eslint-plugin-no-only-tests`](https://github.com/levibuzolic/eslint-plugin-no-only-tests)
+
+</details></td>
+<td valign="top">🟨</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>TypeScript</strong></summary>
+
+[`@typescript-eslint`](https://typescript-eslint.io), [`eslint-plugin-erasable-syntax-only`](https://github.com/JoshuaKGoldberg/eslint-plugin-erasable-syntax-only)
+
+</details></td>
+<td valign="top">☑️</td>
+<td valign="top">🎨</td>
+<td valign="top">💭</td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Unicorn</strong></summary>
+
+[`eslint-plugin-unicorn`](https://github.com/sindresorhus/eslint-plugin-unicorn)
+
+</details></td>
+<td valign="top">✅</td>
+<td valign="top"></td>
+<td valign="top"></td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>Vue</strong></summary>
+
+[`eslint-plugin-vue`](https://eslint.vuejs.org), [`eslint-plugin-vuejs-accessibility`](https://vue-a11y.github.io/eslint-plugin-vuejs-accessibility)
+
+</details></td>
+<td valign="top">☑️ℹ️</td>
+<td valign="top">🎨</td>
+<td valign="top">💭</td>
+</tr>
+<tr>
+<td valign="top">
+<details><summary><strong>YAML</strong></summary>
+
+[`eslint-plugin-yml`](https://ota-meshi.github.io/eslint-plugin-yml)
+
+</details></td>
+<td valign="top">🟨</td>
+<td valign="top">🎨</td>
+<td valign="top"></td>
+</tr>
+</tbody>
+</table>
 
 ## Usage
 
@@ -34,7 +236,7 @@ Flat ESLint config for JavaScript, TypeScript, Vue, React, and more.
 > I like to use [Bun](https://bun.sh) because it's hella fast. Thus all the install instructions are with Bun. If you use something else, check the syntax with your favorite package manager.
 
 ```bash
-bun add -dev eslint @moso/eslint-config
+bun add -d eslint @moso/eslint-config
 ```
 
 Create `eslint.config.js` in the root of your project:
@@ -81,7 +283,6 @@ export default moso(
 
 </details>
 
-
 ### Add script for package.json
 
 For example:
@@ -147,7 +348,7 @@ Add the following settings to your `.vscode/settings.json`:
 
 ## Customization
 
-Since v1.0, this config has been migrated to [ESLint Flat config](https://eslint.org/docs/latest/use/configure/configuration-files-new). It provides much better organization and composition. And speed!
+Since v1.0.0, this config has been migrated to [ESLint Flat config](https://eslint.org/docs/latest/use/configure/configuration-files-new). It provides much better organization and composition. And speed!
 
 Normally you only need to import the `moso` preset:
 
@@ -158,42 +359,42 @@ import moso from '@moso/eslint-config';
 export default moso();
 ```
 
-If you want more control, you can configure each intetegration, like so:
+### Configuration Options
+
+Configure integrations by passing options to the main function:
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
 export default moso({
-    // Disable stylistic formatting rules
-    stylistic: false,
-
-    // Or customize the stylistic rules
+    // Stylistic rules (enabled by default)
+    stylistic: false, // disable entirely
     stylistic: {
         indent: 2, // 4, or 'tab'
         quotes: 'single', // or 'double'
     },
 
-    // TypeScript, Vue, and React are auto-detected, you can also explicitly enable them:
+    // Auto-detected, or enable explicitly
     typescript: true,
     react: true,
     vue: true,
 
-    // Disable jsonc and yaml support
+    // File format support
     jsonc: false,
     yaml: false,
 
-    // `.eslintignore` is no longer supported in Flat config, use `ignores` instead
+    // Replaces .eslintignore (no longer supported)
     ignores: [
         '**/dist',
-        // ...globs
+        '**/node_modules',
     ],
 });
 ```
 
-### Rules overrides
+### Overriding Rules
 
-The `moso` configurator function accepts any number of custom config overrides. And certain rules will only be enabled for specific file types. Example, `vue/*` rules are only applied on `.vue`-files. If you want to override the rules, you need to specify the file extension:
+Pass additional flat config objects as arguments. Rules are scoped to specific file types:
 
 ```js
 // eslint.config.js
@@ -201,55 +402,54 @@ import moso from '@moso/eslint-config';
 
 export default moso(
     {
-        // First argument are configurations for moso's config
+        // First argument: moso config options
         vue: true,
         typescript: true,
     },
     {
-        // Second argument and beyond are ESLint Flat Configs
-        // You can have as many as you want here.
-
-        // Example of overriding vue/* rules on `.vue`-files using the Vue file glob:
+        // Additional arguments: standard ESLint flat configs
         files: ['**/*.vue'],
         rules: {
             'vue/multi-word-component-names': ['error', { ignores: [] }],
         },
     },
     {
-        rules: {},
+        // You can pass multiple config objects
+        files: ['**/*.ts'],
+        rules: {
+            '@typescript-eslint/no-explicit-any': 'warn',
+        },
     },
 );
 ```
 
-Since v1.0.0, the configurator function returns a `FlatConfigComposer`-object from [antfu](https://github.com/antfu)'s [`eslint-flat-config-utils`](https://github.com/antfu/eslint-flat-config-utils#composer), which gives you even more flexibility when composing the config, as you can `dot` your way through:
+### Advanced Composition
+
+The config returns a `FlatConfigComposer` object from [`eslint-flat-config-utils`](https://github.com/antfu/eslint-flat-config-utils#composer), enabling chainable methods:
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
 export default moso()
-    .prepend(
+    .prepend({
         // Configs before the main config
-    )
-    .override(
-        // Override any named config
-        'moso/javascript/rules',
-        {
-            rules: {
-                'no-var': 'off',
-            },
+    })
+    .override('moso/javascript/rules', {
+        rules: {
+            'no-var': 'off',
         },
-    )
-    // You can also remove rules entirely
+    })
     .removeRules(
-        // ...
+        'no-console',
+        'no-debugger',
     );
 ```
 
 <details>
-<summary>Advanced example</summary>
+<summary>Fine-grained config imports</summary>
 
-You can import fine-grained configs and compose them as you want. Don't do this unless you know exactly what you're doing.
+You can import and compose individual configs directly. Only use this if you need granular control:
 
 ```js
 import {
@@ -271,17 +471,17 @@ import {
 } from '@moso/eslint-config';
 
 export default combine(
+    comments(),
     ignores(),
+    imports(),
     javascript(/* options */),
-    comments(),
-    node(),
     jsdoc(),
-    imports(),
-    unicorn(),
+    jsonc(),
+    node(),
+    stylistic(/* options */),
     typescript(/* options */),
-    stylistic(),
+    unicorn(),
     vue(/* options */),
-    jsonc(),
     yaml(),
 );
 ```
@@ -290,112 +490,101 @@ export default combine(
 
 ## Optional configs
 
-There are multiple configs that are deemed "optional". Most of them are set to `true` (enabled), some are `auto-detect`. An example of auto-detection, TypeScript, Vue, and React are set to `auto-detect`, as there are checks in those configs and enable them if their packages are present. But should you want to enable/disable these explicitly, or if my check doesn't auto-detect it, this is how it's done:
+Framework support is auto-detected based on installed packages, but can be enabled explicitly. Dependencies are not bundled and will be prompted for installation.
+
+### React
+
+Auto-detected if you have Gatsby, Next.js, Nextra, React, or Remix installed. Enable explicitly:
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
 export default moso({
-    // Enable TypeScript
-    typescript: true,
-
-    // Enable Vue
-    vue: true,
-
-    // Enable React
     react: true,
 });
 ```
 
-**Note**: Since Vue 2 has [reached EOL](https://v2.vuejs.org/eol), this config does not support Vue 2. If you need to support for Vue 2, you'll need to disable the imported configs from Vue 3, and replace them with the Vue 2 ones. You can see an inspiring example on [`eslint-plugin-vue`](https://eslint.vuejs.org/user-guide/#usage). I recommend upgrading to Vue 3 if possible.
-
-## Optional rules
+Install dependencies when prompted, or manually:
 
-This config also provides some optional plugins/rules for extended usage.
-
-### Perfectionist
+```bash
+bun add --dev @eslint-react/eslint-plugin eslint-plugin-react-hooks eslint-plugin-react-refresh eslint-plugin-react-you-might-not-need-an-effect
+```
 
-The plugin [`eslint-plugin-perfectionist`](https://perfectionist.dev) allows you to sort object keys, imports, types, enums and JSX props with auto fix. I love it, and encourage everyone to use it. It gives you a lot more consistency across projects and developers. The plugin is installed and enabled by default, but only rules for sorting imports are activated.
+### Vue
 
-If you wish to override or extend it, you can by overriding the `perfectionist` integration, or adding to your own `rules`.
+Auto-detected if you have Nuxt, VitePress, or Vue installed. Enable explicitly:
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
-export default moso(
-    {
-        // Overriding the sort-imports
-        perfectionist: {
-            overrides: {
-                'perfectionist/sort-imports': 'off',
-            },
-        },
-    },
-    {
-        // Or adding your own rules
-        rules: {
-            'perfectionist/sort-enums': ['error', { type: 'natural', order: 'asc', locales: 'da-DK' }],
-        },
-    },
-);
+export default moso({
+    vue: true,
+});
 ```
 
-However, you can also opt-in to a rule in each file individually using [configuration comments](https://eslint.org/docs/latest/use/configure/rules#using-configuration-comments-1).
+Install dependencies when prompted, or manually:
 
-```js
-/* eslint perfectionist/sort-objects: 'error' */
-const objectWantedToSort = {
-    a: 2,
-    b: 1,
-    c: 3,
-};
+```bash
+bun add --dev eslint-plugin-vue vue-eslint-parser eslint-processor-vue-blocks eslint-merge-processors
 ```
 
-**Note**: If you want to disable it, you can do it in two ways.
-
-#### Individually
+**Note**: Since Vue 2 has [reached EOL](https://v2.vuejs.org/eol), this config does not support Vue 2. If you need to support for Vue 2, you'll need to disable the imported configs from Vue 3, and replace them with the Vue 2 ones. You can see an inspiring example on [`eslint-plugin-vue`](https://eslint.vuejs.org/user-guide/#usage). I recommend upgrading to Vue 3 if possible.
 
-```js
-// eslint.config.js
-import moso from '@moso/eslint-config';
+### Typed Linting
 
-export default moso({
-    // Disable Perfectionist
-    perfectionist: false,
-});
-```
+You can optionally enable [typed linting](https://typescript-eslint.io/getting-started/typed-linting). These are also known as "rules that require types", or simply "type-aware rules". This enables for much deeper insight into your code.
 
-#### Part of `lessOpinionated`
+You enable them by passing the path of your `tsconfig.json` to the `projectRoot` option.
 
-There's an option to actually make this config "less opinionated". This will also strip most of the [`@stylistic`](https://eslint.style) rules, but more about that at the [Less Opnionated](#i-want-it-less-opnionated)-section.
+> [!WARNING]
+> Enabling these rules will come with a slight performance cost, [explained here](https://typescript-eslint.io/getting-started/typed-linting/#performance).
+>
+> To make things even more complicated, if you have enabled typed linting but disabled [`@stylistic`](https://eslint.style), it will also disable the type-aware rules [considered stylistic](https://typescript-eslint.io/rules/?=stylistic-typeInformation).
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
-export default moso({
-    // Less opnionated
-    lessOpnionated: true,
-});
+export default moso(
+    {
+        projectRoot: import.meta.dirname,
+
+        // If you wish to override any of these rules, use `overridesTypeAware`:
+        typescript: {
+            overridesTypeAware: {
+                '@typescript-eslint/no-deprecated': 'off',
+            },
+        },
+    },
+);
 ```
 
-### Type-aware rules
+> [!NOTE]
+> TypeScript will still be auto-detected if you have the `typescript`-package installed, and any non-type-aware `@typescript-eslint`-rules will still be applied. *Typed Linting* is considered as an extra option.
 
-You can also optionally enable the [type-aware rules](https://typescript-eslint.io/linting/typed-linting) by passing the path of your `tsconfig.json` to the `typescript` config.
+#### Disable type-aware
 
-This enables for much deeper insight into your code.
+Optionally, you can even disable type-aware rules on certain file extensions, or even specific files:
 
 ```js
 // eslint.config.js
 import moso from '@moso/eslint-config';
 
-export default moso({
-    typescript: {
-        tsconfigPath: 'tsconfig.json',
+export default moso(
+    {
+        projectRoot: import.meta.dirname,
     },
-});
+    {
+        files: ['**/*.{js,jsx}'],
+        disableTypeAware: true,
+    },
+    {
+        files: ['**/components/User.jsx'],
+        disableTypeAware: true,
+    },
+);
 ```
 
 ### Editor specific non-fixes
@@ -406,7 +595,7 @@ Some rules are deemed as 'non-fixable' when inside your editor with ESLint integ
 - [`unused-imports/no-unused-imports`](https://github.com/sweepline/eslint-plugin-unused-imports)
 - [`vitest/no-only-tests`](https://github.com/levibuzolic/eslint-plugin-no-only-tests)
 
-This is to prevent unused imports from getting removed by your editor when refactoring to get a better developer experience. However, the rules will still be applied when you run ESLint from your terminal. You can disable this behavior like so:
+Before v1.0.0, they used to be hard disabled. But with a [helper](https://github.com/antfu/eslint-flat-config-utils#composerdisablerulesfix), they are now just marked as 'non-fixable'. They are re-applied when you're linting through a terminal, or by using [Lint Staged](#lint-staged).
 
 ```js
 // eslint.config.js
@@ -453,7 +642,7 @@ bunx @eslint/config-inspector
 
 ## FAQ
 
-### I want it less opnionated
+### I want it less opinionated
 
 No problem. I've extracted the things that I've deemed *very opinionated* in each integration, and made a setting that helps you disable all of it in one go.
 
@@ -466,6 +655,21 @@ export default moso({
 });
 ```
 
+> [!NOTE]
+> The above will also disable `functional` and `perfectionist` completely. If you want to keep these enabled, you'll have to re-enable them explicitly, as demonstrated below
+
+```js
+{
+    functional: true, // will default to 'lite' enforcement
+
+    // Optionally change the `functionalEnforcement`:
+    functionalEnforcement: 'recommended',
+
+    // Re-enable `perfectionist`
+    perfectionist: true,
+}
+```
+
 ### Prettier? dprint?
 
 You can still use these to format files that aren't linted with this config, however, I strongly recommend you only format your code with ESLint, as Pretter and other AST-reading-then-reprint projects tend to ignore stuff like the original line breaks and might also cause inconsistent diffs when commiting code.
@@ -474,25 +678,36 @@ You can still use these to format files that aren't linted with this config, how
 
 You will need to install and configure [`stylelint`](https://stylelint.io) yourself, unfortunately.
 
+I am actively considering adding linting support for TailwindCSS, however.
+
 ### I prefer `this` or `that` rule
 
-Fine, you can always override the rules locally in your project to fit your needs. If that doesn't cut it, you're welcome to fork this project and maintain your own config.
+No worries, you can always override the rules locally in your project to fit your needs. If that doesn't cut it, you're welcome to fork this project and maintain your own config.
 
 ## Inspiration
 
-This eslint-config takes inspiration from (and uses some of) [`@antfu/eslint-config`](https://github.com/antfu/eslint-config) and [`@rubiin/eslint-config`](https://github.com/rubiin/eslint-config) respectively. Thank you to everyone who contributed to these configs.
+This ESLint config is heavily inspired by (and uses some of the same logic of):
+
+\- [@antfu/eslint-config](https://github.com/antfu/eslint-config)
+\- [@rebeccastevens/eslint-config](https://github.com/RebeccaStevens/eslint-config-rebeccastevens)
+\- [@eslint-sukka/eslint-config](https://github.com/SukkaW/eslint-config-sukka)
+
+[Anthony Fu](https://github.com/antfu)'s config inspired me to take the journey, but this project has since evolved into a personal project. Especially Rebecca's config and strict(er) approach to coding has pushed me towards a stricter coding environment, with [Functional](https://github.com/eslint-functional/eslint-plugin-functional) and [Azat](https://github.com/azat-io)'s [Perfectionist](https://perfectionist.dev) and [De Morgan](https://github.com/azat-io/eslint-plugin-de-morgan) enabled.
+
+A personal thank-you to Anthony, Rebecca, Sukka, and Azat, and everyone else who contributed to their projects.
 
-*Most* of the rules are the same, however, there are some differences:
+*Some* rules are the same, however, there are some differences:
 
-- Opinionated rules
-- Enables Stylistic per default
-- React detection, no need to enable it
-- Includes dependencies rather than asking you to install them
+- My own opinionated rules added
+- Stylistic, Perfectionist, and Functional enabled per default
+- More freedom to disable every individual config, or only disable the opinionated parts
 - Deprecated Vue 2 support
 - Simplification in some areas
-- Less clutter, shipping with less "smart" features
-- No dangerous plugin renaming, except for `eslint-plugin-n` which is renamed to `node` for readability
+- Better type-aware checks
+- Plugin memoization
+- Optional a11y support for React and Vue
+- No dangerous plugin renaming
 
 ## License
 
-[MIT](./LICENSE) License
+[BSD 3-Clause](./LICENSE) License