Solution 1: with Lerna you can use workspace and Lerna yarn workspace & lerna ├── README.md ├── lerna.json ├── package.json ├── packages │ ├── pdf │ │ ├── package.json /* “shared-ts”: “^1.0.0” */ │ │ └── src │ ├── frontend │ │ ├── package.json │ │ └── src │ ├── mobile │ │ ├── package.json … Read more
I think I might have something here, this is the solution I’ve adopted after some back ‘n forth with the NRWL team. I create an NX workspace by first creating a project with the angular CLI, and then adding the extensions, like so: ng new myproject (cd into myproject root) ng add @nrwl/workspace In addition, … Read more
I’ve worked on a project following a structure similar to yours, it was looking like: project ├── package.json ├── packages │ ├── package1 │ │ ├── package.json │ │ └── src │ ├── package2 │ │ ├── package.json │ │ └── src │ └── package3 │ ├── package.json │ └── src ├── services │ … Read more
2022 Update As pointed out by my great fellow at the comment section, Lerna is now being held by the Nx team. The best solution nowadays is to use more native approaches for publishing (as NPM/YARN workspaces) or go straight to Nx. Good references: Lerna is dead — Long Live Lerna Integrating Nx and Lerna … Read more