npm - @spscommerce/eslint-config-typescript - Versions diffs - 9.2.3 → 9.3.0 - Mend

@spscommerce/eslint-config-typescript 9.2.3 → 9.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2) hide show

package/GUIDE.md +116 -116
package/package.json +1 -1

package/GUIDE.md CHANGED Viewed

@@ -493,7 +493,7 @@ console.log(foo[0], bar[0]); // => 9, 9
 <a name="types--assertions"></a>
 [**1.3**](#types--assertions) ‣ Type assertions should be written in `as` style, rather than prefix style.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/consistent-type-assertions`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/consistent-type-assertions.md)
+[`@typescript-eslint/consistent-type-assertions`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/consistent-type-assertions.md)
 > Why? Because it uses angle brackets, the prefix style can be confused when generics are also in play, as well as potentially tripping up IDEs and tooling in `.tsx` files.
@@ -516,7 +516,7 @@ console.log(squareIt(foo as number));
 <a name="types--enums"></a>
 [**1.4**](#types--enums) ‣ Explicitly initialize the values of enum members.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/prefer-enum-initializers`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/prefer-enum-initializers.md)
+[`@typescript-eslint/prefer-enum-initializers`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/prefer-enum-initializers.md)
 > Why? If you allow member values to be inferred, then adding a new member can result in the values of pre-existing members changing. This can potentially introduce bugs.
@@ -542,7 +542,7 @@ enum Status {
 <a name="references--prefer-const"></a>
 [**2.1**](#references--prefer-const) ‣ Use `const` for all of your references; avoid using `var`.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-const`](https://eslint.org/docs/rules/prefer-const.html), [`no-const-assign`](https://eslint.org/docs/rules/no-const-assign.html)
+[`prefer-const`](https://eslint.org/docs/rules/prefer-const.html), [`no-const-assign`](https://eslint.org/docs/rules/no-const-assign.html)
 > Why? This ensures that you can’t reassign your references, which can lead to bugs and difficult to comprehend code.
@@ -561,7 +561,7 @@ const b = 2;
 <a name="references--disallow-var"></a>
 [**2.2**](#references--disallow-var) ‣ If you must reassign references, use `let` instead of `var`.
-<img src="../eslint.svg" height="18" align="center"/> [`no-var`](https://eslint.org/docs/rules/no-var.html)
+[`no-var`](https://eslint.org/docs/rules/no-var.html)
 > Why? `let` is block-scoped rather than function-scoped like `var`.
@@ -605,7 +605,7 @@ In the above code, you can see that referencing `a` and `b` will produce a Refer
 <a name="objects--no-new"></a>
 [**3.1**](#objects--no-new) ‣ Use the literal syntax for object creation.
-<img src="../eslint.svg" height="18" align="center"/> [`no-new-object`](https://eslint.org/docs/rules/no-new-object.html)
+[`no-new-object`](https://eslint.org/docs/rules/no-new-object.html)
 ```typescript
 // bad
@@ -647,7 +647,7 @@ const obj = {
 <a name="es6-object-shorthand"></a>
 [**3.3**](#es6-object-shorthand) ‣ Use object method shorthand.
-<img src="../eslint.svg" height="18" align="center"/> [`object-shorthand`](https://eslint.org/docs/rules/object-shorthand.html)
+[`object-shorthand`](https://eslint.org/docs/rules/object-shorthand.html)
 ```typescript
 // bad
@@ -674,7 +674,7 @@ const atom = {
 <a name="es6-object-concise"></a>
 [**3.4**](#es6-object-concise) ‣ Use property value shorthand.
-<img src="../eslint.svg" height="18" align="center"/> [`object-shorthand`](https://eslint.org/docs/rules/object-shorthand.html)
+[`object-shorthand`](https://eslint.org/docs/rules/object-shorthand.html)
 > Why? It is shorter and descriptive.
@@ -697,9 +697,9 @@ const obj = {
 <a name="objects--quoted-props"></a>
 [**3.5**](#objects--quoted-props) ‣ Only quote properties that are invalid identifiers.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`quote-props`](https://eslint.org/docs/rules/quote-props.html)
+[`quote-props`](https://eslint.org/docs/rules/quote-props.html)
 > Why? In general we consider it subjectively easier to read. It improves syntax highlighting, and is also more easily optimized by many JS engines.
@@ -724,7 +724,7 @@ const good = {
 <a name="objects--rest-spread"></a>
 [**3.6**](#objects--rest-spread) ‣ Prefer the object spread syntax over [`Object.assign`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign) to shallow-copy objects. Use the object rest operator to get a new object with certain properties omitted.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-object-spread`](https://eslint.org/docs/rules/prefer-object-spread)
+[`prefer-object-spread`](https://eslint.org/docs/rules/prefer-object-spread)
 ```typescript
 // very bad
@@ -750,7 +750,7 @@ const { a, ...noA } = copy; // noA => { b: 2, c: 3 }
 <a name="arrays--literals"></a>
 [**4.1**](#arrays--literals) ‣ Use the literal syntax for array creation, except in the case of initializing a sparse array with a specific size.
-<img src="../eslint.svg" height="18" align="center"/> [`no-array-constructor`](https://eslint.org/docs/rules/no-array-constructor.html)
+[`no-array-constructor`](https://eslint.org/docs/rules/no-array-constructor.html)
 ```typescript
 // bad
@@ -845,7 +845,7 @@ const baz = Array.from(foo, bar);
 <a name="arrays--callback-return"></a>
 [**4.7**](#arrays--callback-return) ‣ Use return statements in array method callbacks. It’s ok to omit the return if the function body consists of a single statement returning an expression without side effects, following [**9.2**](#arrows--implicit-return).
-<img src="../eslint.svg" height="18" align="center"/> [`array-callback-return`](https://eslint.org/docs/rules/array-callback-return)
+[`array-callback-return`](https://eslint.org/docs/rules/array-callback-return)
 ```typescript
 // good
@@ -892,7 +892,7 @@ inbox.filter((msg) => {
 <a name="arrays--bracket-newline"></a>
 [**4.8**](#arrays--bracket-newline) ‣ Use line breaks after open and before close array brackets if an array has multiple lines.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 ```typescript
 // bad
@@ -934,7 +934,7 @@ const stringInArray = [
 <a name="arrays--sort-compare"></a>
 [**4.9**](#arrays--sort-compare) ‣ Always provide a comparison function to `Array#sort`.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/require-array-sort-compare`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/require-array-sort-compare.md)
+[`@typescript-eslint/require-array-sort-compare`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/require-array-sort-compare.md)
 > Why? `Array#sort` is one of those old-school Javascript things that does not behave the way you would expect. If you don't pass in your own comparison function, it converts all the contents to strings and sorts alphabetically.
@@ -955,7 +955,7 @@ const ahThatsBetter = [30, 10, 3, 2, 20, 1].sort((a, b) => a - b);
 <a name="destructuring--object"></a>
 [**5.1**](#destructuring--object) ‣ Use object destructuring when accessing and using multiple properties of an object.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-destructuring`](https://eslint.org/docs/rules/prefer-destructuring)
+[`prefer-destructuring`](https://eslint.org/docs/rules/prefer-destructuring)
 > Why? Destructuring saves you from creating temporary references for those properties, and from repetitive access of the object. Repeating object access creates more repetitive code, requires more reading, and creates more opportunities for mistakes. Destructuring objects also provides a single site of definition of the object structure that is used in the block, rather than requiring reading the entire block to determine what is used.
@@ -985,7 +985,7 @@ function getFullName({ firstName, lastName }) {
 <a name="destructuring--array"></a>
 [**5.2**](#destructuring--array) ‣ Use array destructuring.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-destructuring`](https://eslint.org/docs/rules/prefer-destructuring)
+[`prefer-destructuring`](https://eslint.org/docs/rules/prefer-destructuring)
 ```typescript
 const arr = [1, 2, 3, 4];
@@ -1032,9 +1032,9 @@ const { left, top } = processInput(input);
 <a name="strings--quotes"></a>
 [**6.1**](#strings--quotes) ‣ Use double quotes `""` for strings.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`quotes`](https://eslint.org/docs/rules/quotes.html)
+[`quotes`](https://eslint.org/docs/rules/quotes.html)
 > Why? In a JSX world, double quotes result in your code needing fewer escapes than single quotes.
@@ -1077,7 +1077,7 @@ const errorMessage = "This is a super long error that was thrown because of Batm
 <a name="es6-template-literals"></a>
 [**6.3**](#es6-template-literals) ‣ When programmatically building up strings, use template strings instead of concatenation.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-template`](https://eslint.org/docs/rules/prefer-template.html), [`template-curly-spacing`](https://eslint.org/docs/rules/template-curly-spacing)
+[`prefer-template`](https://eslint.org/docs/rules/prefer-template.html), [`template-curly-spacing`](https://eslint.org/docs/rules/template-curly-spacing)
 > Why? Template strings give you a readable, concise syntax with proper newlines and string interpolation features.
@@ -1108,16 +1108,16 @@ function sayHi(name) {
 <a name="strings--eval"></a>
 [**6.4**](#strings--eval) ‣ Never use `eval()` on a string, it opens too many vulnerabilities.
-<img src="../eslint.svg" height="18" align="center"/> [`no-eval`](https://eslint.org/docs/rules/no-eval)
+[`no-eval`](https://eslint.org/docs/rules/no-eval)
 ---
 <a name="strings--escaping"></a>
 [**6.5**](#strings--escaping) ‣ Do not unnecessarily escape characters in strings.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`no-useless-escape`](https://eslint.org/docs/rules/no-useless-escape)
+[`no-useless-escape`](https://eslint.org/docs/rules/no-useless-escape)
 > Why? Backslashes harm readability, thus they should only be present when necessary.
@@ -1137,7 +1137,7 @@ const foo = `my name is '${name}'`;
 <a name="promises--handle-errors"></a>
 [**7.1**](#promises--handle-errors) ‣ When awaiting a promise, the potential for it to be rejected must be handled.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/no-floating-promises`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-floating-promises.md)
+[`@typescript-eslint/no-floating-promises`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-floating-promises.md)
 > Why? We've all seen "Unhandled Promise rejection" before and not once has that error ever been useful in debugging the issue. Do yourself a favor and catch Promise errors so you can at least log out a useful error object.
@@ -1187,7 +1187,7 @@ void someBackendCall();
 <a name="functions--in-blocks"></a>
 [**8.1**](#functions--in-blocks) ‣ Never declare a function in a non-function block (`if`, `while`, etc). Assign the function to a variable instead. Browsers will allow you to do it, but they all interpret it differently, which is bad news bears.
-<img src="../eslint.svg" height="18" align="center"/> [`no-loop-func`](https://eslint.org/docs/rules/no-loop-func.html)
+[`no-loop-func`](https://eslint.org/docs/rules/no-loop-func.html)
 ---
@@ -1216,7 +1216,7 @@ if (currentUser) {
 <a name="es6-rest"></a>
 [**8.3**](#es6-rest) ‣ Never use `arguments`, opt to use rest syntax `...` instead.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-rest-params`](https://eslint.org/docs/rules/prefer-rest-params)
+[`prefer-rest-params`](https://eslint.org/docs/rules/prefer-rest-params)
 > Why? `...` is explicit about which arguments you want pulled. Plus, rest arguments are a real Array, and not merely Array-like like `arguments`.
@@ -1288,7 +1288,7 @@ count();  // 3
 <a name="functions--defaults-last"></a>
 [**8.6**](#functions--defaults-last) ‣ Always put default parameters last.
-<img src="../eslint.svg" height="18" align="center"/> [`default-param-last`](https://eslint.org/docs/rules/default-param-last)
+[`default-param-last`](https://eslint.org/docs/rules/default-param-last)
 ```typescript
 // bad
@@ -1307,7 +1307,7 @@ function handleThings(name: string, opts: IHandleThingsOpts = {}) {
 <a name="functions--constructor"></a>
 [**8.7**](#functions--constructor) ‣ Never use the Function constructor to create a new function.
-<img src="../eslint.svg" height="18" align="center"/> [`no-new-func`](https://eslint.org/docs/rules/no-new-func)
+[`no-new-func`](https://eslint.org/docs/rules/no-new-func)
 > Why? Creating a function in this way evaluates a string similarly to `eval()`, which opens vulnerabilities.
@@ -1324,9 +1324,9 @@ const subtract = Function("a", "b", "return a - b");
 <a name="functions--signature-spacing"></a>
 [**8.8**](#functions--signature-spacing) ‣ Spacing in a function signature.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`space-before-function-paren`](https://eslint.org/docs/rules/space-before-function-paren), [`space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks)
+[`space-before-function-paren`](https://eslint.org/docs/rules/space-before-function-paren), [`space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks)
 > Why? Consistency is good, and you shouldn’t have to add or remove a space when adding or removing a name.
@@ -1346,7 +1346,7 @@ const y = function a() {};
 <a name="functions--mutate-params"></a>
 [**8.10**](#functions--mutate-params) ‣ Never mutate parameters.
-<img src="../eslint.svg" height="18" align="center"/> [`no-param-reassign`](https://eslint.org/docs/rules/no-param-reassign.html)
+[`no-param-reassign`](https://eslint.org/docs/rules/no-param-reassign.html)
 > Why? Manipulating objects passed in as parameters can cause unwanted variable side effects in the original caller.
@@ -1372,7 +1372,7 @@ function f2(obj: ObjType) {
 <a name="functions--reassign-params"></a>
 [**8.11**](#functions--reassign-params) ‣ Never reassign parameters.
-<img src="../eslint.svg" height="18" align="center"/> [`no-param-reassign`](https://eslint.org/docs/rules/no-param-reassign.html)
+[`no-param-reassign`](https://eslint.org/docs/rules/no-param-reassign.html)
 > Why? Reassigning parameters can lead to unexpected behavior, especially when accessing the `arguments` object. It can also cause optimization issues, especially in V8.
@@ -1404,7 +1404,7 @@ function f4(a: number = 1) {
 <a name="functions--spread-vs-apply"></a>
 [**8.12**](#functions--spread-vs-apply) ‣ Prefer the use of the spread syntax `...` to call variadic functions.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-spread`](https://eslint.org/docs/rules/prefer-spread)
+[`prefer-spread`](https://eslint.org/docs/rules/prefer-spread)
 > Why? It’s cleaner, you don’t need to supply a context, and you can not easily compose `new` with `apply`.
@@ -1429,7 +1429,7 @@ new Date(...[2016, 8, 5]);
 <a name="functions--signature-invocation-indentation"></a>
 [**8.13**](#functions--signature-invocation-indentation) ‣ Functions with multiline signatures, or invocations, should be indented just like every other multiline list in this guide: with each item on a line by itself, with a trailing comma on the last item.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 ```typescript
 // bad
@@ -1466,7 +1466,7 @@ console.log(
 <a name="functions--return-type"></a>
 [**8.14**](#functions--return-type) ‣ Functions and methods should include an explicit return type.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/explicit-function-return-type`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/explicit-function-return-type.md)
+[`@typescript-eslint/explicit-function-return-type`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/explicit-function-return-type.md)
 > Why? If you explicitly specify what the function is intended to return, then a bug where it returns something unintended will be caught immediately in your IDE. If you allow TypeScript to infer the return type, it will assume anything the function ends up returning is fine. (We acknowledge the examples throughout this document often don't follow this. Time permitting we will possibly correct that.)
@@ -1498,7 +1498,7 @@ function foo(isTwo: boolean): number {
 <a name="arrows--use-them"></a>
 [**9.1**](#arrows--use-them) ‣ When you must use an anonymous function (as when passing an inline callback), use arrow function notation.
-<img src="../eslint.svg" height="18" align="center"/> [`prefer-arrow-callback`](https://eslint.org/docs/rules/prefer-arrow-callback.html), [`arrow-spacing`](https://eslint.org/docs/rules/arrow-spacing.html)
+[`prefer-arrow-callback`](https://eslint.org/docs/rules/prefer-arrow-callback.html), [`arrow-spacing`](https://eslint.org/docs/rules/arrow-spacing.html)
 > Why? It creates a version of the function that executes in the context of `this`, which is usually what you want, and is a more concise syntax.
@@ -1523,7 +1523,7 @@ function foo(isTwo: boolean): number {
 <a name="arrows--implicit-return"></a>
 [**9.2**](#arrows--implicit-return) ‣ If the function body consists of a single statement returning an [expression](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Expressions_and_Operators#Expressions) without side effects, omit the braces and use the implicit return. Otherwise, keep the braces and use a `return` statement.
-<img src="../eslint.svg" height="18" align="center"/> [`arrow-parens`](https://eslint.org/docs/rules/arrow-parens.html), [`arrow-body-style`](https://eslint.org/docs/rules/arrow-body-style.html)
+[`arrow-parens`](https://eslint.org/docs/rules/arrow-parens.html), [`arrow-body-style`](https://eslint.org/docs/rules/arrow-body-style.html)
 > Why? Syntactic sugar. It reads well when multiple functions are chained together.
@@ -1596,9 +1596,9 @@ foo(() => {
 <a name="arrows--one-arg-parens"></a>
 [**9.4**](#arrows--one-arg-parens) ‣ Always include parentheses around arguments for clarity and consistency.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`arrow-parens`](https://eslint.org/docs/rules/arrow-parens.html)
+[`arrow-parens`](https://eslint.org/docs/rules/arrow-parens.html)
 > Why? Minimizes diff churn when adding or removing arguments.
@@ -1637,7 +1637,7 @@ foo(() => {
 <a name="arrows--confusing"></a>
 [**9.5**](#arrows--confusing) ‣ Avoid confusing arrow function syntax (`=>`) with comparison operators (`<=`, `>=`).
-<img src="../eslint.svg" height="18" align="center"/> [`no-confusing-arrow`](https://eslint.org/docs/rules/no-confusing-arrow)
+[`no-confusing-arrow`](https://eslint.org/docs/rules/no-confusing-arrow)
 ```typescript
 // bad
@@ -1661,7 +1661,7 @@ const itemHeight = (item: ItemType) => {
 <a name="arrows--implicit-arrow-linebreak"></a>
 [**9.6**](#arrows--implicit-arrow-linebreak) ‣ Enforce the location of arrow function bodies with implicit returns.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 ```typescript
 // bad
@@ -1811,7 +1811,7 @@ class Jedi {
 <a name="constructors--no-useless"></a>
 [**10.5**](#constructors--no-useless) ‣ Classes have a default constructor if one is not specified. An empty constructor function or one that just delegates to a parent class is unnecessary.
-<img src="../eslint.svg" height="18" align="center"/> [`no-useless-constructor`](https://eslint.org/docs/rules/no-useless-constructor)
+[`no-useless-constructor`](https://eslint.org/docs/rules/no-useless-constructor)
 ```typescript
 // bad
@@ -1846,7 +1846,7 @@ class Rey extends Jedi {
 <a name="classes--no-duplicate-members"></a>
 [**10.6**](#classes--no-duplicate-members) ‣ Avoid duplicate class members.
-<img src="../eslint.svg" height="18" align="center"/> [`no-dupe-class-members`](https://eslint.org/docs/rules/no-dupe-class-members)
+[`no-dupe-class-members`](https://eslint.org/docs/rules/no-dupe-class-members)
 > Why? Duplicate class member declarations will silently prefer the last one - having duplicates is almost certainly a bug.
@@ -1873,7 +1873,7 @@ class Foo {
 <a name="classes--methods-use-this"></a>
 [**10.7**](#classes--methods-use-this) ‣ Class methods should use `this` or be made into a static method unless an external library or framework requires using specific non-static methods. Being an instance method should indicate that it behaves differently based on properties of the receiver.
-<img src="../eslint.svg" height="18" align="center"/> [`class-methods-use-this`](https://eslint.org/docs/rules/class-methods-use-this)
+[`class-methods-use-this`](https://eslint.org/docs/rules/class-methods-use-this)
 ```typescript
 // bad
@@ -1933,7 +1933,7 @@ export default es6;
 <a name="modules--no-duplicate-imports"></a>
 [**11.2**](#modules--no-duplicate-imports) ‣ Only import from a path in one place.
-<img src="../eslint.svg" height="18" align="center"/> [`no-duplicate-imports`](https://eslint.org/docs/rules/no-duplicate-imports)
+[`no-duplicate-imports`](https://eslint.org/docs/rules/no-duplicate-imports)
 > Why? Having multiple lines that import from the same path can make code harder to maintain.
@@ -1958,7 +1958,7 @@ import foo, {
 <a name="modules--no-mutable-exports"></a>
 [**11.3**](#modules--no-mutable-exports) ‣ Do not export mutable bindings.
-<img src="../eslint.svg" height="18" align="center"/> [`import/no-mutable-exports`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md)
+[`import/no-mutable-exports`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md)
 > Why? Mutation should be avoided in general, but in particular when exporting mutable bindings. While this technique may be needed for some special cases, in general, only constant references should be exported.
@@ -1977,7 +1977,7 @@ export { foo };
 <a name="modules--imports-first"></a>
 [**11.4**](#modules--imports-first) ‣ Put all `import`s above non-import statements.
-<img src="../eslint.svg" height="18" align="center"/> [`import/first`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/first.md)
+[`import/first`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/first.md)
 > Why? Since `import`s are hoisted, keeping them all at the top prevents surprising behavior.
@@ -2000,7 +2000,7 @@ foo.init();
 <a name="modules--multiline-imports-over-newlines"></a>
 [**11.5**](#modules--multiline-imports-over-newlines) ‣ Multiline imports should be indented just like multiline array and object literals.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 > Why? The curly braces follow the same indentation rules as every other curly brace block in the style guide, as do the trailing commas.
@@ -2026,7 +2026,7 @@ Note: formerly we used [`object-curly-newline`](https://eslint.org/docs/rules/ob
 <a name="modules--no-webpack-loader-syntax"></a>
 [**11.6**](#modules--no-webpack-loader-syntax) ‣ Disallow Webpack loader syntax in module import statements.
-<img src="../eslint.svg" height="18" align="center"/> [`import/no-webpack-loader-syntax`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-webpack-loader-syntax.md)
+[`import/no-webpack-loader-syntax`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-webpack-loader-syntax.md)
 > Why? Since using Webpack syntax in the imports couples the code to a module bundler. Prefer using the loader syntax in `webpack.config.js`.
@@ -2045,7 +2045,7 @@ import barCss from "bar.css";
 <a name="modules--import-extensions"></a>
 [**11.7**](#modules--import-extensions) ‣ Do not include JavaScript filename extensions
-<img src="../eslint.svg" height="18" align="center"/> [`import/extensions`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/extensions.md)
+[`import/extensions`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/extensions.md)
   > Why? Including extensions inhibits refactoring, and inappropriately hardcodes implementation details of the module you're importing in every consumer.
@@ -2116,7 +2116,7 @@ const increasedByOne = numbers.map((num) => num + 1);
 <a name="iterators--no-for-in"></a>
 [**12.2**](#iterators--no-for-in) ‣ Do not use `for-in`.
-<img src="../eslint.svg" height="18" align="center"/> [`no-restricted-syntax`](https://eslint.org/docs/rules/no-restricted-syntax)
+[`no-restricted-syntax`](https://eslint.org/docs/rules/no-restricted-syntax)
 > Why? `for-in` has confusing and unexpected behavior. For this reason, `for-of` was added to the language and should be used instead.
@@ -2151,9 +2151,9 @@ for (const [key, value] of Object.entries(obj)) {
 <a name="generators--spacing"></a>
 [**12.3**](#generators--spacing) ‣ A generator's function signature should be spaced with `function*` as a single unit surrounded by spaces.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`generator-star-spacing`](https://eslint.org/docs/rules/generator-star-spacing)
+[`generator-star-spacing`](https://eslint.org/docs/rules/generator-star-spacing)
 > Why? `function` and `*` are part of the same conceptual keyword - `*` is not a modifier for `function`, `function*` is a unique construct, different from `function`.
@@ -2220,7 +2220,7 @@ const foo = function* () {
 <a name="properties--dot"></a>
 [**13.1**](#properties--dot) ‣ Use dot notation when accessing properties.
-<img src="../eslint.svg" height="18" align="center"/> [`dot-notation`](https://eslint.org/docs/rules/dot-notation.html)
+[`dot-notation`](https://eslint.org/docs/rules/dot-notation.html)
 ```typescript
 const luke = {
@@ -2243,7 +2243,7 @@ const isJedi = luke.jedi;
 <a name="variables--const"></a>
 [**14.1**](#variables--const) ‣ Always use `const` or `let` to declare variables. Not doing so will result in global variables. We want to avoid polluting the global namespace. Captain Planet warned us of that.
-<img src="../eslint.svg" height="18" align="center"/> [`no-undef`](https://eslint.org/docs/rules/no-undef), [`prefer-const`](https://eslint.org/docs/rules/prefer-const)
+[`no-undef`](https://eslint.org/docs/rules/no-undef), [`prefer-const`](https://eslint.org/docs/rules/prefer-const)
 ```typescript
 // bad
@@ -2258,7 +2258,7 @@ const superPower = new SuperPower();
 <a name="variables--one-const"></a>
 [**14.2**](#variables--one-const) ‣ Use one `const` or `let` declaration per variable or assignment.
-<img src="../eslint.svg" height="18" align="center"/> [`one-var`](https://eslint.org/docs/rules/one-var.html)
+[`one-var`](https://eslint.org/docs/rules/one-var.html)
 > Why? It’s easier to add new variable declarations this way, and you never have to worry about swapping out a `;` for a `,` or introducing punctuation-only diffs. You can also step through each declaration with the debugger, instead of jumping through all of them at once.
@@ -2352,7 +2352,7 @@ function checkName(hasName) {
 <a name="variables--no-chain-assignment"></a>
 [**14.5**](#variables--no-chain-assignment) ‣ Don’t chain variable assignments.
-<img src="../eslint.svg" height="18" align="center"/> [`no-multi-assign`](https://eslint.org/docs/rules/no-multi-assign)
+[`no-multi-assign`](https://eslint.org/docs/rules/no-multi-assign)
 > Why? Chaining variable assignments creates implicit global variables.
@@ -2389,7 +2389,7 @@ console.log(c); // throws ReferenceError
 <a name="variables--unary-increment-decrement"></a>
 [**14.6**](#variables--unary-increment-decrement) ‣ Avoid using unary increments and decrements (`++`, `--`).
-<img src="../eslint.svg" height="18" align="center"/> [`no-plusplus`](https://eslint.org/docs/rules/no-plusplus)
+[`no-plusplus`](https://eslint.org/docs/rules/no-plusplus)
 > Why? Per the eslint documentation, unary increment and decrement statements are subject to automatic semicolon insertion and can cause silent errors with incrementing or decrementing values within an application. It is also more expressive to mutate your values with statements like `num += 1` instead of `num++` or `num ++`. Disallowing unary increment and decrement statements also prevents you from pre-incrementing/pre-decrementing values unintentionally which can also cause unexpected behavior in your programs.
@@ -2427,7 +2427,7 @@ const truthyCount = array.filter(Boolean).length;
 <a name="variables--linebreak"></a>
 [**14.7**](#variables--linebreak) ‣ Avoid linebreaks before or after `=` in an assignment. If your assignment violates [`max-len`](https://eslint.org/docs/rules/max-len.html), surround the value in parens.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 > Why? Linebreaks surrounding `=` can obfuscate the value of an assignment.
@@ -2454,7 +2454,7 @@ const foo = "superLongLongLongLongLongLongLongLongString";
 <a name="variables--no-unused-vars"></a>
 [**14.8**](#variables--no-unused-vars) ‣ Disallow unused variables.
-<img src="../eslint.svg" height="18" align="center"/> [`no-unused-vars`](https://eslint.org/docs/rules/no-unused-vars)
+[`no-unused-vars`](https://eslint.org/docs/rules/no-unused-vars)
 > Why? Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.
@@ -2499,7 +2499,7 @@ const { type, ...coords } = data;
 <a name="comparison--eqeqeq"></a>
 [**15.1**](#comparison--eqeqeq) ‣ Use `===` and `!==` over `==` and `!=`.
-<img src="../eslint.svg" height="18" align="center"/> [`eqeqeq`](https://eslint.org/docs/rules/eqeqeq.html)
+[`eqeqeq`](https://eslint.org/docs/rules/eqeqeq.html)
 ---
@@ -2625,7 +2625,7 @@ switch (foo) {
 <a name="comparison--nested-ternaries"></a>
 [**15.6**](#comparison--nested-ternaries) ‣ Ternaries should not be nested and generally be single line expressions.
-<img src="../eslint.svg" height="18" align="center"/> [`no-nested-ternary`](https://eslint.org/docs/rules/no-nested-ternary.html)
+[`no-nested-ternary`](https://eslint.org/docs/rules/no-nested-ternary.html)
 ```typescript
 // bad
@@ -2650,7 +2650,7 @@ const foo = maybe1 > maybe2 ? "bar" : maybeNull;
 <a name="comparison--unneeded-ternary"></a>
 [**15.7**](#comparison--unneeded-ternary) ‣ Avoid unneeded ternary statements.
-<img src="../eslint.svg" height="18" align="center"/> [`no-unneeded-ternary`](https://eslint.org/docs/rules/no-unneeded-ternary.html)
+[`no-unneeded-ternary`](https://eslint.org/docs/rules/no-unneeded-ternary.html)
 ```typescript
 // bad
@@ -2667,7 +2667,7 @@ const baz = !c;
 <a name="comparison--no-mixed-operators"></a>
 [**15.8**](#comparison--no-mixed-operators) ‣ When mixing operators, enclose them in parentheses. The only exception is the standard arithmetic operators: `+`, `-`, and `**` since their precedence is broadly understood. We recommend enclosing `/` and `*` in parentheses because their precedence can be ambiguous when they are mixed.
-<img src="../eslint.svg" height="18" align="center"/> [`no-mixed-operators`](https://eslint.org/docs/rules/no-mixed-operators.html)
+[`no-mixed-operators`](https://eslint.org/docs/rules/no-mixed-operators.html)
 > Why? This improves readability and clarifies the developer’s intention.
@@ -2707,7 +2707,7 @@ const bar = a + (b / c) * d;
 <a name="comparison--nullish-coalescing"></a>
 [**15.9**](#comparison--nullish-coalescing) ‣ Use the nullish coalescing operator over `||`. If you do need to coalesce over a falsy value that is not `null` or `undefined`, use a ternary that defines the desired condition explicitly.
-<img src="../eslint.svg" height="18" align="center"/> [`@typescript-eslint/prefer-nullish-coalescing`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/prefer-nullish-coalescing.md)
+[`@typescript-eslint/prefer-nullish-coalescing`](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/prefer-nullish-coalescing.md)
 ```typescript
 // bad
@@ -2727,9 +2727,9 @@ const foo = typeof foo === "string" && foo !== "" ? foo : "baz";
 <a name="blocks--cuddled-elses"></a>
 [**16.1**](#blocks--cuddled-elses) ‣ If you’re using multiline blocks with `if` and `else`, put `else` on the same line as your `if` block’s closing brace.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`brace-style`](https://eslint.org/docs/rules/brace-style.html)
+[`brace-style`](https://eslint.org/docs/rules/brace-style.html)
 ```typescript
 // bad
@@ -2757,7 +2757,7 @@ if (test) {
 <a name="control-statements"></a>
 [**17.1**](#control-statements) ‣ In case your control statement (`if`, `while` etc.) gets too long or exceeds the maximum line length, each (grouped) condition could be put into a new line.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
 > Why? This improves readability by making it easier to visually follow complex logic.
@@ -2897,7 +2897,7 @@ function getType() {
 <a name="comments--spaces"></a>
 [**18.3**](#comments--spaces) ‣ Start all comments with a space to make it easier to read.
-<img src="../eslint.svg" height="18" align="center"/> [`spaced-comment`](https://eslint.org/docs/rules/spaced-comment)
+[`spaced-comment`](https://eslint.org/docs/rules/spaced-comment)
 ```typescript
 // bad
@@ -2967,9 +2967,9 @@ class Calculator extends Abacus {
 <a name="whitespace--spaces"></a>
 [**19.1**](#whitespace--spaces) ‣ Use soft tabs (space character) set to 2 spaces.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`indent`](https://eslint.org/docs/rules/indent.html)
+[`indent`](https://eslint.org/docs/rules/indent.html)
 ```typescript
 // bad
@@ -2993,9 +2993,9 @@ function baz() {
 <a name="whitespace--before-blocks"></a>
 [**19.2**](#whitespace--before-blocks) ‣ Place 1 space before the leading brace.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks.html)
+[`space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks.html)
 ```typescript
 // bad
@@ -3026,9 +3026,9 @@ dog.set("attr", {
 <a name="whitespace--around-keywords"></a>
 [**19.3**](#whitespace--around-keywords) ‣ Place 1 space before the opening parenthesis in control statements (`if`, `while` etc.). Place no space between the argument list and the function name in function calls and declarations.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`keyword-spacing`](https://eslint.org/docs/rules/keyword-spacing.html)
+[`keyword-spacing`](https://eslint.org/docs/rules/keyword-spacing.html)
 ```typescript
 // bad
@@ -3057,9 +3057,9 @@ function fight() {
 <a name="whitespace--infix-ops"></a>
 [**19.4**](#whitespace--infix-ops) ‣ Set off operators with spaces.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`space-infix-ops`](https://eslint.org/docs/rules/space-infix-ops.html)
+[`space-infix-ops`](https://eslint.org/docs/rules/space-infix-ops.html)
 ```typescript
 // bad
@@ -3074,9 +3074,9 @@ const x = y + 5;
 <a name="whitespace--newline-at-end"></a>
 [**19.5**](#whitespace--newline-at-end) ‣ End files with a single newline character.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`eol-last`](https://github.com/eslint/eslint/blob/master/docs/rules/eol-last.md)
+[`eol-last`](https://github.com/eslint/eslint/blob/master/docs/rules/eol-last.md)
 ```typescript
 // bad
@@ -3105,9 +3105,9 @@ export default es6;↵
 <a name="whitespace--chains"></a>
 [**19.6**](#whitespace--chains) ‣ Use indentation when making long method chains (more than 2 method chains). Use a leading dot, which emphasizes that the line is a method call, not a new statement.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`newline-per-chained-call`](https://eslint.org/docs/rules/newline-per-chained-call), [`no-whitespace-before-property`](https://eslint.org/docs/rules/no-whitespace-before-property)
+[`newline-per-chained-call`](https://eslint.org/docs/rules/newline-per-chained-call), [`no-whitespace-before-property`](https://eslint.org/docs/rules/no-whitespace-before-property)
 ```typescript
 // bad
@@ -3194,9 +3194,9 @@ return arr;
 <a name="whitespace--padded-blocks"></a>
 [**19.8**](#whitespace--padded-blocks) ‣ Do not pad your blocks with blank lines.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`padded-blocks`](https://eslint.org/docs/rules/padded-blocks.html)
+[`padded-blocks`](https://eslint.org/docs/rules/padded-blocks.html)
 ```typescript
 // bad
@@ -3242,9 +3242,9 @@ if (baz) {
 <a name="whitespace--no-multiple-blanks"></a>
 [**19.9**](#whitespace--no-multiple-blanks) ‣ Do not use multiple blank lines to pad your code.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`no-multiple-empty-lines`](https://eslint.org/docs/rules/no-multiple-empty-lines)
+[`no-multiple-empty-lines`](https://eslint.org/docs/rules/no-multiple-empty-lines)
 ```typescript
 // bad
@@ -3311,9 +3311,9 @@ class Person {
 <a name="whitespace--in-parens"></a>
 [**19.10**](#whitespace--in-parens) ‣ Do not add spaces inside parentheses.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`space-in-parens`](https://eslint.org/docs/rules/space-in-parens.html)
+[`space-in-parens`](https://eslint.org/docs/rules/space-in-parens.html)
 ```typescript
 // bad
@@ -3342,9 +3342,9 @@ if (foo) {
 <a name="whitespace--in-brackets"></a>
 [**19.11**](#whitespace--in-brackets) ‣ Do not add spaces inside brackets.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`array-bracket-spacing`](https://eslint.org/docs/rules/array-bracket-spacing.html)
+[`array-bracket-spacing`](https://eslint.org/docs/rules/array-bracket-spacing.html)
 ```typescript
 // bad
@@ -3361,9 +3361,9 @@ console.log(foo[0]);
 <a name="whitespace--in-braces"></a>
 [**19.12**](#whitespace--in-braces) ‣ Add spaces inside curly braces.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`object-curly-spacing`](https://eslint.org/docs/rules/object-curly-spacing.html)
+[`object-curly-spacing`](https://eslint.org/docs/rules/object-curly-spacing.html)
 ```typescript
 // bad
@@ -3380,7 +3380,7 @@ const foo = { clark: "kent" };
 Prettier does not enforce this specifically, but will wrap lines at _roughly_ 80 characters, meaning that after it has done its formatting your code will - except in extremely rare circumstances - fit within the 100 character limit. Please refer to [Prettier's documentation on the print width option](https://prettier.io/docs/en/options.html#print-width) for more information.
-<img src="../eslint.svg" height="18" align="center"/> [`max-len`](https://eslint.org/docs/rules/max-len.html)
+[`max-len`](https://eslint.org/docs/rules/max-len.html)
 > Why? This ensures readability and maintainability.
@@ -3402,9 +3402,9 @@ const foo = jsonData
 <a name="whitespace--comma-spacing"></a>
 [**19.14**](#whitespace--comma-spacing) ‣ Avoid spaces before commas and require a space after commas.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`comma-spacing`](https://eslint.org/docs/rules/comma-spacing)
+[`comma-spacing`](https://eslint.org/docs/rules/comma-spacing)
 ```typescript
 // bad
@@ -3419,9 +3419,9 @@ const arr = [1, 2];
 <a name="whitespace--computed-property-spacing"></a>
 [**19.15**](#whitespace--computed-property-spacing) ‣ Enforce spacing inside of computed property brackets.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`computed-property-spacing`](https://eslint.org/docs/rules/computed-property-spacing)
+[`computed-property-spacing`](https://eslint.org/docs/rules/computed-property-spacing)
 ```typescript
 // bad
@@ -3442,9 +3442,9 @@ obj[foo[bar]]
 <a name="whitespace--func-call-spacing"></a>
 [**19.16**](#whitespace--func-call-spacing) ‣ Avoid spaces between functions and their invocations.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`func-call-spacing`](https://eslint.org/docs/rules/func-call-spacing)
+[`func-call-spacing`](https://eslint.org/docs/rules/func-call-spacing)
 ```typescript
 // bad
@@ -3462,9 +3462,9 @@ func();
 <a name="whitespace--key-spacing"></a>
 [**19.17**](#whitespace--key-spacing) ‣ Enforce spacing between keys and values in object literal properties.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`key-spacing`](https://eslint.org/docs/rules/key-spacing)
+[`key-spacing`](https://eslint.org/docs/rules/key-spacing)
 ```typescript
 // bad
@@ -3480,9 +3480,9 @@ const obj = { foo: 42 };
 <a name="whitespace--no-trailing-spaces"></a>
 [**19.18**](#whitespace--no-trailing-spaces) ‣ Avoid trailing spaces at the end of lines.
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`no-trailing-spaces`](https://eslint.org/docs/rules/no-trailing-spaces)
+[`no-trailing-spaces`](https://eslint.org/docs/rules/no-trailing-spaces)
 ```typescript
 // bad
@@ -3500,9 +3500,9 @@ const foo = "bar";
 <a name="commas--leading-trailing"></a>
 [**20.1**](#commas--leading-trailing) ‣ Leading commas: **Nope.**
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`comma-style`](https://eslint.org/docs/rules/comma-style.html)
+[`comma-style`](https://eslint.org/docs/rules/comma-style.html)
 ```typescript
 // bad
@@ -3541,9 +3541,9 @@ const hero = {
 <a name="commas--dangling"></a>
 [**20.2**](#commas--dangling) ‣ Additional trailing comma: **Yup.**
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`comma-dangle`](https://eslint.org/docs/rules/comma-dangle.html)
+[`comma-dangle`](https://eslint.org/docs/rules/comma-dangle.html)
 > Why? This leads to cleaner git diffs.
@@ -3645,9 +3645,9 @@ createHero(
 <a name="semicolons--required"></a>
 [**21.1**](#semicolons--required) ‣ **Yup.**
-<img src="../prettier.svg" height="18" align="center"/> **Enforced by Prettier**
+**Enforced by Prettier**
-<img src="../eslint.svg" height="18" align="center"/> [`semi`](https://eslint.org/docs/rules/semi.html)
+[`semi`](https://eslint.org/docs/rules/semi.html)
 > Why? When JavaScript encounters a line break without a semicolon, it uses a set of rules called [Automatic Semicolon Insertion](https://tc39.github.io/ecma262/#sec-automatic-semicolon-insertion) to determine whether it should regard that line break as the end of a statement, and (as the name implies) place a semicolon into your code before the line break if it thinks so. ASI contains a few eccentric behaviors, though, and your code will break if JavaScript misinterprets your line break. These rules will become more complicated as new features become a part of JavaScript. Explicitly terminating your statements and configuring your linter to catch missing semicolons will help prevent you from encountering issues.
@@ -3704,7 +3704,7 @@ function foo() {
 <a name="coercion--strings"></a>
 [**22.2**](#coercion--strings) ‣ Strings:
-<img src="../eslint.svg" height="18" align="center"/> [`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
+[`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
 ```typescript
 // => this.reviewScore = 9;
@@ -3727,7 +3727,7 @@ const totalScore = String(this.reviewScore);
 <a name="coercion--numbers"></a>
 [**22.3**](#coercion--numbers) ‣ Numbers: Use `Number` for type casting and `parseInt` always with a radix for parsing strings.
-<img src="../eslint.svg" height="18" align="center"/> [`radix`](https://eslint.org/docs/rules/radix), [`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
+[`radix`](https://eslint.org/docs/rules/radix), [`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
 > Why? The `parseInt` function produces an integer value dictated by interpretation of the contents of the string argument according to the specified radix. Leading whitespace in string is ignored. If radix is `undefined` or `0`, it is assumed to be `10` except when the number begins with the character pairs `0x` or `0X`, in which case a radix of 16 is assumed. This differs from ECMAScript 3, which merely discouraged (but allowed) octal interpretation. Many implementations have not adopted this behavior as of 2013. And, because older browsers must be supported, always specify a radix.
@@ -3784,7 +3784,7 @@ const val = inputValue >> 0;
 <a name="coercion--booleans"></a>
 [**22.6**](#coercion--booleans) ‣ Booleans:
-<img src="../eslint.svg" height="18" align="center"/> [`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
+[`no-new-wrappers`](https://eslint.org/docs/rules/no-new-wrappers)
 ```typescript
 const age = 0;
@@ -3806,7 +3806,7 @@ const hasAge = !!age;
 <a name="naming--descriptive"></a>
 [**23.1**](#naming--descriptive) ‣ Avoid single letter names. Be descriptive with your naming.
-<img src="../eslint.svg" height="18" align="center"/> [`id-length`](https://eslint.org/docs/rules/id-length)
+[`id-length`](https://eslint.org/docs/rules/id-length)
 ```typescript
 // bad
@@ -3825,7 +3825,7 @@ function query() {
 <a name="naming--camelCase"></a>
 [**23.2**](#naming--camelCase) ‣ Use camelCase when naming objects, functions, and instances.
-<img src="../eslint.svg" height="18" align="center"/> [`camelcase`](https://eslint.org/docs/rules/camelcase.html)
+[`camelcase`](https://eslint.org/docs/rules/camelcase.html)
 ```typescript
 // bad
@@ -3843,7 +3843,7 @@ function thisIsMyFunction() {}
 <a name="naming--PascalCase"></a>
 [**23.3**](#naming--PascalCase) ‣ Use PascalCase only when naming constructors or classes.
-<img src="../eslint.svg" height="18" align="center"/> [`new-cap`](https://eslint.org/docs/rules/new-cap.html)
+[`new-cap`](https://eslint.org/docs/rules/new-cap.html)
 ```typescript
 // bad
@@ -3872,7 +3872,7 @@ const good = new User({
 <a name="naming--leading-underscore"></a>
 [**23.4**](#naming--leading-underscore) ‣ Do not use trailing or leading underscores.
-<img src="../eslint.svg" height="18" align="center"/> [`no-underscore-dangle`](https://eslint.org/docs/rules/no-underscore-dangle.html)
+[`no-underscore-dangle`](https://eslint.org/docs/rules/no-underscore-dangle.html)
 > Why? Although a leading underscore has long been a common convention to mean “private”, in fact, these properties are fully public, and as such, are part of your public API contract. This convention might lead developers to wrongly think that a change won’t count as breaking, or that tests aren’t needed. tl;dr: if you want something to be “private”, it must not be observably present. With the addition of private class fields in ES2022, there is a genuine way to do this, so the informal convention is obsolete.
@@ -4181,7 +4181,7 @@ contains utilities that are functionally broken but remain for legacy reasons.
 [**26.1**](#standard-library--isnan) ‣ Use `Number.isNaN` instead of global `isNaN`.
-<img src="../eslint.svg" height="18" align="center"/> [`no-restricted-globals`](https://eslint.org/docs/rules/no-restricted-globals)
+[`no-restricted-globals`](https://eslint.org/docs/rules/no-restricted-globals)
 > Why? The global `isNaN` coerces non-numbers to numbers, returning true for anything that coerces to NaN.
 > If this behavior is desired, make it explicit.
@@ -4201,7 +4201,7 @@ Number.isNaN(Number("1.2.3")); // true
 <a name="standard-library--isfinite"></a>
 [**26.2**](#standard-library--isfinite) ‣ Use `Number.isFinite` instead of global `isFinite`.
-<img src="../eslint.svg" height="18" align="center"/> [`no-restricted-globals`](https://eslint.org/docs/rules/no-restricted-globals)
+[`no-restricted-globals`](https://eslint.org/docs/rules/no-restricted-globals)
 > Why? The global `isFinite` coerces non-numbers to numbers, returning true for anything that coerces to a finite number.
 > If this behavior is desired, make it explicit.

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@spscommerce/eslint-config-typescript",
-  "version": "9.2.3",
+  "version": "9.3.0",
   "description": "SPS official linter configuration for TypeScript.",
   "main": "lib/index.js",
   "exports": {