Registro de cambios

Version 2.3.14 Latest

Patch Changes

#8921 29e2435 Thanks @siketyan! - Fixed #8759: The useConsistentTypeDefinitions rule no longer converts empty object type declarations into interfaces, as it will conflict with the noEmptyInterface rule and can cause an infinite loop when both rules are enabled.
#8928 ccaeac4 Thanks @taga3s! - Added the nursery rule useGlobalThis. This rule enforces using globalThis over window, self and global.
#8602 9a18daa Thanks @dyc3! - Added the new nursery rule noVueArrowFuncInWatch. This rule forbids using arrow functions in watchers in Vue components, because arrow functions do not give access to the component instance (via this), while regular functions do.
#8905 9b1eea8 Thanks @ryan-m-walker! - Fixed #8428: Improved parsing recovery when encountering qualified rules inside CSS @page at-rule blocks.
#8900 f788cff Thanks @mdevils! - Fixed #8802: useExhaustiveDependencies now correctly suggests dependencies without including callback-scoped variables or method names.

When accessing object properties with a callback-scoped variable, only the object path is suggested:
```
1
// Now correctly suggests `props.value` instead of `props.value[day]`
2
useMemo(() => {
3
  return WeekdayValues.filter((day) => props.value[day]);
4
}, [props.value]);
```
When calling methods on objects, only the object is suggested as a dependency:
```
1
// Now correctly suggests `props.data` instead of `props.data.forEach`
2
useMemo(() => {
3
  props.data.forEach((item) => console.log(item));
4
}, [props.data]);
```
#8913 e1e20ea Thanks @dyc3! - Fixed #8363: HTML parser no longer crashes when encountering a < character followed by a digit in text content (e.g., <12 months). The parser now correctly emits an “Unescaped < bracket character” error instead of treating <12 as a tag name and crashing.
#8910 2fb63a4 Thanks @dyc3! - Fixed #8774: Type aliases with generic parameters that have extends constraints now properly indent comments after the equals sign.

Previously, comments after the = in type aliases with extends constraints were not indented:
```
1
type A<B, C extends D> = // Some comment
2
undefined;
3
type A<B, C extends D> =
4
    // Some comment
5
    undefined;
```
#8916 ea4bd04 Thanks @ryan-m-walker! - Fixed #4013, where comments in member chains caused unnecessary line breaks.
```
1
// Before
2
aFunction.b().c.d();
3

4
// After
5
aFunction.b().c.d();
```

#8945 fa66fe3 Thanks @fireairforce! - Fixed #8354: Don’t remove quotes when type memeber is new.

1
// Input:
2
type X = {
3
  "new"(): string;
4
  "foo"(): string;
5
};
6

7
// Format Output:
8
type X = {
9
  "new()": string;
10
  foo(): string;
11
};

#8927 0ef3da5 Thanks @littleKitchen! - Fixed #8907: useExhaustiveDependencies now correctly recognizes stable hook results (like useState setters and useRef values) when declared with let.
#8931 4561751 Thanks @koshin01! - Added the new nursery rule noRedundantDefaultExport, which flags redundant default exports where the default export references the same identifier as a named export.

#8900 f788cff Thanks @mdevils! - Fixed #8883: useExhaustiveDependencies no longer produces false positives when props are destructured in the function body of arrow function components without parentheses around the parameter.

1
type Props = { msg: string };
2

3
// Arrow function without parentheses around `props`
4
const Component: React.FC<Props> = (props) => {
5
  const { msg } = props;
6
  // Previously, this incorrectly reported `msg` as unnecessary
7
  useEffect(() => console.log(msg), [msg]);
8
};

#8861 3531687 Thanks @dyc3! - Added the noDeprecatedMediaType CSS rule to flag deprecated media types like tv and handheld.
#8775 7ea71cd Thanks @igas! - Fixed the noUnnecessararyConditions rule to prevent trigger for optional fallback patterns.
#8860 95f1eea Thanks @dyc3! - Added the nursery rule noHexColors, which flags the use of hexadecimal color codes in CSS and suggests using named colors or RGB/RGBA/HSL/HSLA formats instead.
#8786 d876a38 Thanks @Bertie690! - Added the nursery rule useConsistentMethodSignatures.
Inspired by the similarly named version from typescript-eslint, this rule aims to enforce a consistent style for methods used inside object types and interfaces.

Examples

Invalid code with style set to "property" (the default):
```
1
interface Foo {
2
  method(a: string): void;
3
}
```
Invalid code with style set to "method":
```
1
type Bar = {
2
  prop: (a: string) => void;
3
}
```
#8864 5e97119 Thanks @dyc3! - Improved the summary provided by biome migrate eslint to be clearer on why rules were not migrated. Biome now specifies a reason when a rule is not migrated, such as being incompatible with the formatter or not implemented yet. This helps users make more informed decisions when migrating their ESLint configurations to Biome.
#8924 99b4cd1 Thanks @tmohammad78! - Fixed #8920: noUnknownFunction now knows about sibling-count, and sibling-index css functions

#8900 f788cff Thanks @mdevils! - Fixed #8885: useExhaustiveDependencies no longer incorrectly reports variables as unnecessary dependencies when they are derived from expressions containing post/pre-increment operators (++/--) or compound assignment operators (+=, -=, etc.).

1
let renderCount = 0;
2

3
export const MyComponent = () => {
4
  // `count` is now correctly recognized as a required dependency
5
  // because `renderCount++` can produce different values between renders
6
  const count = renderCount++;
7

8
  useEffect(() => {
9
    console.log(count);
10
  }, [count]); // no longer reports `count` as unnecessary
11
};

#8619 d78e01d Thanks @Netail! - Added the nursery rule useInputName. Require mutation arguments to be called “input”, and the input type to be called Mutation name + “Input”.

Invalid:
```
1
type Mutation {
2
  SetMessage(message: String): String
3
}
```
#8922 871b45e Thanks @siketyan! - Fixed #8829: Revamped the noGlobalDirnameFilename rule to catch many false negatives that have not been reported.

Registro de cambios

Version 2.3.14 Latest

Patch Changes

Examples