|
| 1 | +--- |
| 2 | +id: legacy-package-management |
| 3 | +title: Legacy Package Management |
| 4 | +type: recipe |
| 5 | +--- |
| 6 | + |
| 7 | +# Legacy Package Management |
| 8 | + |
| 9 | +## Background |
| 10 | + |
| 11 | +Lerna is the original monorepo/workspace tool in the JavaScript ecosystem. When it was created in 2015/2016 the ecosystem looked totally different, and there were no built in capabilities to handle working with multiple packages in a single repository (a "workspace"). Commands like lerna bootstrap, lerna add and lerna link were all a critical part of the lerna project, because there were no other options. |
| 12 | + |
| 13 | +However, now that we find ourselves in late 2022, the fact is that - for many years now - the package managers we know and love (`npm`, `yarn` and `pnpm`) all fully support that concept of workspaces as a first-class use-case. |
| 14 | + |
| 15 | +They have battle tested implementations covering adding, removing and linking local packages, and combining them with third party dependencies in a natural way. |
| 16 | + |
| 17 | +This is the reason why, for the past several years of his tenure as lead maintainer of Lerna, Daniel, has been encouraging folks to strongly reconsider their use of the legacy package management commands in lerna, and instead leverage their package manager of choice to do what it does best. |
| 18 | + |
| 19 | +We knew about this context from afar, but as new stewards of the project we did not want to jump straight in and start removing capabilities without first taking the time to get familiar with the reality up close. Now that we have been actively maintaining the project for half a year, we are in full agreement with Daniel and others that the legacy package management commands in lerna need to be retired. |
| 20 | + |
| 21 | +By removing these legacy pieces which have better alternatives natively in package managers, we and the rest of the lerna community will be freed up to concentrate our efforts on things which are uniquely valuable about lerna (such as, but not limited to, versioning and publishing), and making them the best they can be! |
| 22 | + |
| 23 | +From version 7, therefore, we will no longer ship the legacy package management commands (such as lerna bootstrap, lerna add and lerna link) by default with lerna, and instead make them available as an add-on via a separate package (name TBD). |
| 24 | + |
| 25 | +This new package can be thought of as being in maintenance mode only - no new features will be considered for legacy package management concerns (such as lerna bootstrap, lerna add and lerna link), and we will only look to merge critical patches and security updates. |
| 26 | + |
| 27 | +:::info |
| 28 | + |
| 29 | +This same context is covered on the [Lerna v7 discussion](https://github.com/lerna/lerna/discussions/3410), if you have any specific concerns, please join us there and provide as much information as possible! |
| 30 | + |
| 31 | +::: |
| 32 | + |
| 33 | +## Legacy Bootstrap Command |
| 34 | + |
| 35 | +Lerna's legacy bootstrap command links different projects within the repo so they can import each other without having to publish anything to NPM. To show how Lerna does it, we will take [this repository](https://github.com/lerna/getting-started-example) as an example. |
| 36 | + |
| 37 | +The repo contains three packages or projects: |
| 38 | + |
| 39 | +- `header` (a library of React components) |
| 40 | +- `footer` (a library of React components) |
| 41 | +- `remixapp` (an app written using the Remix framework which depends on both `header` and `footer`) |
| 42 | + |
| 43 | +The Remix app imports the `header` and `footer` libraries as follows: |
| 44 | + |
| 45 | +```typescript jsx title="packages/remixapp/app/routes/index.tsx" |
| 46 | +import { Header } from "header"; |
| 47 | +import { Footer } from "footer"; |
| 48 | + |
| 49 | +export default function Index() { |
| 50 | + return ( |
| 51 | + <> |
| 52 | + <Header /> |
| 53 | + <div>Content!</div> |
| 54 | + <Footer /> |
| 55 | + </> |
| 56 | + ); |
| 57 | +} |
| 58 | +``` |
| 59 | + |
| 60 | +And it depends on them in its `package.json` as follows: |
| 61 | + |
| 62 | +```json title="packages/remixapp/package.json" |
| 63 | +{ |
| 64 | + "dependencies": { |
| 65 | + "@remix-run/node": "^1.5.1", |
| 66 | + "@remix-run/react": "^1.5.1", |
| 67 | + "@remix-run/serve": "^1.5.1", |
| 68 | + "react": "^17.0.2", |
| 69 | + "react-dom": "^17.0.2", |
| 70 | + "header": "*", |
| 71 | + "footer": "*" |
| 72 | + } |
| 73 | +} |
| 74 | +``` |
| 75 | + |
| 76 | +To make the `header` and `footer` available inside the `remixapp`, run: |
| 77 | + |
| 78 | +```bash |
| 79 | +lerna bootstrap --use-workspaces |
| 80 | +``` |
| 81 | + |
| 82 | +This installs all the dependencies needed for the 3 projects and links the `header` and `footer` projects so that `remixapp` can reference them like npm packages. `--use-workspaces` tells Lerna to delegate package linking process to your package manager. (This feature is supported by npm, yarn and pnpm.) |
| 83 | + |
| 84 | +You can also set `useWorkspaces` as the default behavior in the `lerna.json` file: |
| 85 | + |
| 86 | +```json title="lerna.json" |
| 87 | +{ |
| 88 | + ... |
| 89 | + "useWorkspaces": true |
| 90 | +} |
| 91 | +``` |
| 92 | + |
| 93 | +## Other Bootstrapping Methods |
| 94 | + |
| 95 | +Bootstrapping this way should work for most people, but you can use [Alternate Legacy Bootstrapping Methods](../concepts/alternate-bootstrapping-methods) if needed. |
0 commit comments