Contents
What do you mean by sharing code between projects?
Like many other teams, we were working on a few things at a time, developing different projects for our web and mobile applications, with shared ingredients in the form of common Node.js code between our back-end repositoriess and microservices, and common React UI components with some slight visual and functional differences between our apps.
By sharing a common package.json between native and web, you’ve glued them together by their common dependencies, the most important one being react. Let’s say you upgrade to a version of react-native that depends on >= react@16, but your web app depends on some other library which depends on =< react@15.
What are the lessons learned from code sharing?
In this article, Jonathan Saring shares his and his team’s lessons learned from their own journey towards simple and effective code sharing. About a year ago, we came to a crossroad that changed the way we build software today.
Can you publish five different packages from the same repository?
Even though it uses Lerna to publish five different packages from the same repository, you would still have to install the entire library to use each of its components. Making changes would still have to go through that project as well, and discoverability for these component didn’t improve.
If you’re attempting to share code between two different project types (I.e.: desktop project and a mobile project), you may look into the shared solutions folder. I have to do that for my current project as the mobile and desktop projects both require identical classes that are only in 1 file.
By the way , Solution can’t explicitly depend on another solution. If you’re attempting to share code between two different project types (I.e.: desktop project and a mobile project), you may look into the shared solutions folder.