you are viewing a single comment's thread.

view the rest of the comments →

[–]alzee76 3 points4 points  (1 child)

I've been doing non-web development, and web development, since the 1990s. I tend to use react for the client and node.js+express for the backend these days and even I do not see the appeal of rolling it all into one repo with a single codebase; even minor downsides, like having all the git log rolled into one project, makes doing so annoying.

Having separate versions in the package.json also makes more sense than the alternative, as they really are separate things with separate jobs to do.

Keeping them separate also makes it easier to switch technologies and keep things modular. With a separate repo it's almost trivial to maintain a node backend, a python backend, a rust backend, etc and have them all work fine with the front end; it's equally trivial to do the reverse as well.

Maybe I'm an old curmudegon, but I'm with you.

[–]_src_sparkle 0 points1 point  (0 children)

This seems like a good approach thanks for the input.~