Great articles! For my taste also these are good to have: // in .eslintrc.js "extends" : [ ... // already there "plugin:react/recommended" , // warn when rules of hooks are violated "plugin:react-hooks/recommended" , // disable requirements to import react at the top of the file // requires to "npm i -D eslint-plugin-react-hooks" "plugin:react/jsx-runtime" , ] ...

Jordan Brennan Never heard of inert attr. It seems that you can use it like this: <div inert={isInertOn ? "" : undefined }/> https://github.com/WICG/inert/issues/58#issuecomment-618016847 But yes, React compiles to html so dev must rely on the compiler support. I don't often use Web Components but I agree that is a shame that an industry leader library lacks in fundamentals. It seems that something is moving here https://github.com/facebook/react/issues/11347#issuecomment-1122275286 Is a shame that an industry leader library lacks in fundamentals. This is a weird thing, hard to accept honestly, even if 95% of apps never encounter these problems it doesn't mean that these should be ignored. Great points here Jordan.

Really appreciate your honest feedback Jordan. Vue has the plus to be more similar to HTML and you can use it just in a static file using CDN. In React you can't bypass a build tool. To this day it is not fully compatible with Web Components and fails, and has failed many times, to handle certain HTML attributes correctly. I'm curious, which problem did you encounter with React and WebComponents, and React and HTML attributes?