3 ms·
The problems described in the "Routing" section are trivially automated. You do not even need a separate data loading library because react-router-dom ships one
by mikojan 4y ago
The problems described in the "Routing" section are trivially automated. You do not even need a separate data loading library because react-router-dom ships one.
The problems described in the "Styles" section would have been solved by migrating to a modern bundler: vite.
- adchurch 4y ago> The problems described in the "Routing" section are trivially automated. You do not even need a separate data loading library because react-router-dom ships one. I'm not sure which problems you mean; fwiw the routing section is more intended to explain how we migrated `react-router`-style routing to `next/router`-style routing :) > The problems described in the "Styles" section would have been solved by migrating to a modern bundler: vite. I think the problems with impure styles (e.g. `styles/button.scss` referenced in the post) would have been an issue no matter what bundler we used, right? Which problems are you referring to?