For my own project, the solution is to use docker BuildKit to first build all the workspace and then build a docker image for the project workspace reusing the previous built files. In details you have copy in the docker file the top package.json with yarn lock and then cherrypicking the package.json of the needed … Read more
Try running the command npm install –g lerna
You should be able to accomplish this with npm link. Although I have not tried this using a local dependency that is not published on npm. Directory tree foo/ packages/ core/ package.json errors/ package.json bar/ package.json foo/packages/core/package.json { … dependencies: { “@foo/errors”: “*” } } bar/package.json { … dependencies: { “@foo/core”: “../foo/packages/core” } } Run … Read more
NPM has supported workspaces since version 7, for two major releases now. With workspaces, npm i / npm ci takes care of nested packages and symlinking. npm run and npm exec can be run across individual or all workspaces: npm run test –workspace=a –workspace=”name-from-package-dot-json” npm run test –workspaces –if-present With that said, lerna comes with … Read more
NPM 7 is out and it supports workspaces. they will also continue to develop this domain in the upcoming releases, With that said, lerna comes with many more high level features than npm7 or yarn workspaces, furthermore, yarn declared that they will never try to replace tools like lerna, rather they intend to implement the … 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