The latest articles on DEV Community by Pavlo Tymchuk (@letitrock). https://dev.to/letitrock 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%2F104358%2F51311171-0730-4e18-a4b5-e9a0bd3b7376.jpeg https://dev.to/letitrock en Pavlo Tymchuk Tue, 16 Jul 2019 08:25:25 +0000 https://dev.to/letitrock/yarn-workspaces-splitting-react-app-by-routes-55oo https://dev.to/letitrock/yarn-workspaces-splitting-react-app-by-routes-55oo <p>Hello developers! <br> I need your suggestions/help regarding the idea we had in our team. </p> <p>We have a massive React/Redux/Sagas application which weights a lot, so we decided to split it based on routes. But suddenly one idea came to our mind: why not to move those "split routes" code into separate yarn packages (with reducers, sagas, etc)? We thought it would be easier to manage in the future.</p> <p>Splitting code into multiple chunks that would be imported dynamically with Webpack also requires us to implement additional logic for importing reducers and sagas after the chunk is downloaded by the browser, but it's doable.</p> <p>Could you please share your thoughts on this? Does it really make sense to go this way and use yarn workspaces?</p> <p>Thanks!</p> help discuss react yarn