At my workplace, we have a variety of web and mobile projects with unique builds but sharing similar custom frontend components. Currently, we store the code for these projects in the same repository structure:
/root
--/web
--/mobile
--/shared_components
However, this approach doesn't seem sustainable for long-term scalability. Managing both projects individually could become cumbersome.
I considered converting the shared components into a private bower component and including the necessary bower.json files in both repositories. Another idea was to utilize git's subtree feature, but I'm hoping to find a simpler solution that won't overwhelm team members who are still learning git. Using node modules presents the same issue as bower.
If anyone has alternative suggestions, I would greatly appreciate it. Thank you.