What is the best practice for building multiple TS/Node targets (and by "targets", I don't mean ES6 vs ESNext, I mean in the C/C++ sense: multiple output "programs", so in this case I want it to both create the bundle necessary for my RN app, but then also generate a CLI executable.) that all share code with one another, from a single monorepo? The confusion caused by this approach has been a significant drain on productivity, and it feels like there has to be a better way. It gets even more confusing with the TS build folders lying around they're another place for people to import the wrong thing from.
#Taskboard sphere install#
It didn't take long for this to become a total mess, primarily with duplicate imports where one thing mysteriously seems to import modules from the other targets' node_modules, but also just remembering to re- npm install all the different subprojects before each commit, etc. I would like these to live in the same monorepo.īased on advice from colleagues and my own research, I have tried doing this by creating a subfolder in the repo, and creating a second package.json (and all the other config files), and npm install-ing as if it were a completely separate project. I have a React Native app built using TypeScript, and I would like to also develop a number of CLI tools to help developers and 'back office' folks, also using TypeScript.
0 kommentar(er)
