The latest articles on DEV Community by popuguy (@popuguytheparrot). https://dev.to/popuguytheparrot https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F283246%2Fb33ab896-0568-421b-8d25-5434025a773f.jpeg https://dev.to/popuguytheparrot en popuguy Tue, 14 Jun 2022 18:02:43 +0000 https://dev.to/popuguytheparrot/bad-idea-to-upgrade-to-react-router-6-9ln https://dev.to/popuguytheparrot/bad-idea-to-upgrade-to-react-router-6-9ln <p>I have not been so burned from the decision to update the dependencies of the project for a long time and it was react router</p> <p>As with version 3, the developers decided that since the major, without a code mod, you can break everything and not leave backward compatibility</p> <p>After the update, the familiar codebase is highlighted in red (typescript)</p> <p>useHistory is completely cut out, now we need to use a lot of different hooks.<br> If you have class components, then you should either pass through props or create a custom hook where these hooks will be called<br> history.replace now navigate(url, {replace: true})<br> histore.goBack now navigate(-1)<br> state was removed from prop to now it is a separate prop on Link<br> useLocation cannot be typified, in order to pass typing for state through &lt;&gt; now only typecasts</p> <p>oh, I naively thought that the useSearchParams hook signature would make it possible to conveniently work with parameters, but when I opened the example, I didn’t understand anything at all</p> <p>I burn, I have stress and hatred. For me, react-router is dead and is now the worst react library ever. I feel the same way about the remix team.</p> <p><strong>Please developers, don't upgrade and don't use react router in your projects.<br> No more of this pain. Don't use it to instantly turn your routing into a pumpkin</strong></p> react webdev opensource