The getFullyQualifiedName is an underrated TS API that can be used to get a stable signature of the API behind a symbol, whether it's built-in, or from a specific library, or to determine if a type comes from a certain npm package. I learned about it while solving github.com/Rel1cx/eslin...

LLMs don't even dare to think you can use TypeScript tuple to eliminate null from two variables at once 😋 github.com/Rel1cx/eslin...

Two new tsl rules to detect and merge duplicate import and export statements into one

Released ESLint Plugin Perfectionist v5.0.0. 🎉 It’s a plugin for sorting imports, TS types, JSX props, classes, objects, variables, and more. In this release: move to ESM-only, dropped Node.js v18 support, two new rules. github.com/azat-io/esli... More in the thread below ⬇️

If you narrow the children prop's type in ActivityProps, TypeScript will warn you that you can't use bare text as its child

Announcing eslint-react.xyz v2.0.0: Now ESM-Only eslint-react.xyz/docs/release...

A shift is happening: State management is returning to React's built-in APIs, while third-party libraries are pivoting to focus on effect management rather than state management.

This was quite a forward-thinking article at the time—thanks for sharing!

Of all current TS linters, this one comes closest to the "rules as functions" design philosophy This means you can define, document, export, import, hover, jump to definition, and deprecate custom rules (and their options) just like ordinary JavaScript functions with types and JSDoc

A fully functional ReactLynx example, configured to use the rulesets from eslint-react.xyz github.com/Rel1cx/eslin...

Compatibility testing for react-x rules with Lynx and React Strict DOM (RSD) is underway. If everything goes as expected, the rules should naturally support these new platforms without needing any changes, cus we don't make assumptions about the platforms used in your tech stack

Compatibility testing for eslint-plugin-react-x rules with Lynx and React Strict DOM (RSD) is underway. If everything goes as expected, these rules should naturally support these new platforms without needing any changes, because we don't make assumptions about the platforms used in your tech stack.

github.com/drwpow/html-... The best alternative to aria-query for creating accessible HTML based on the [latest ARIA 1.3 specs](www.w3.org/TR/wai-aria-...) and latest [HTML in ARIA](www.w3.org/TR/html-aria/) recommendations. Lightweight, performant, tree-shakeable, and 0 dependencies 🤩

The newly added React 19 rules comes with built-in codemods that let you refactor components to the new APIs right in the editor or by simply running `eslint . --fix` from the terminal eslint-react.xyz/docs/rules/n... eslint-react.xyz/docs/rules/n... eslint-react.xyz/docs/rules/n...

Check out the roadmap for version 2.0 here eslint-react.xyz/roadmap#mile...

It's been a year since the 1.0 release of eslint-react.xyz 🎉