The only React-related problems the article describes are API changes (which are generally announced via deprecation messages if you don&#x27;t skip several releases when upgrading) and invalid DOM nesting (which is just React becoming less messy).<p>Everything else seems to be the result of forcing a square peg in a round hole, i.e. using non-standard tooling. As much as I can understand the desire to have one set of tooling to rule them all, if I were using Ruby&#x2F;Python&#x2F;PHP&#x2F;Java for my backend I wouldn&#x27;t expect to be able to integrate my backend tooling with the Gulp&#x2F;Grunt&#x2F;WebPack I might use to build the frontend. Expecting to be able to do the same the other way around is just as arrogant, especially if you then blame the ecosystem you&#x27;re trying to avoid for the incompatibilities you&#x27;re experiencing.