Organized the image handling + color palette generation on the backend into their own modules for ease of readability. This should hopefully make it easier to setup and debug extra things later like AWS.
I also did some package + code cleanup, and chose to replace @reach/router with react-router v6, which absorbed reach router anyways. The purpose of reach router was that it is a lighter package, but v6 supports that too now with tree-shaking. When doing research into the package, it seems like people are having stable experiences with it, despite it being in beta stage technically. On some Auth0 tutorials they mention react-router parts, so that's another reason why I'm choosing to switch, for ease and consistency.
carbonsoda
commented
3 years ago 
Organized the image handling + color palette generation on the backend into their own modules for ease of readability. This should hopefully make it easier to setup and debug extra things later like AWS.
I also did some package + code cleanup, and chose to replace
@reach/routerwithreact-routerv6, which absorbed reach router anyways. The purpose of reach router was that it is a lighter package, but v6 supports that too now with tree-shaking. When doing research into the package, it seems like people are having stable experiences with it, despite it being in beta stage technically. On some Auth0 tutorials they mention react-router parts, so that's another reason why I'm choosing to switch, for ease and consistency.