npm-to-yarn
npm-to-yarn copied to clipboard
feat: new conversions
The conversions which are not supported are added.
All possible conversions
| to | Supported | Progress | |
|---|---|---|---|
| npm | yarn | ✔ | ✔ |
| npm | pnpm | ✔ | ✔ |
| npm | bun | ✔ | ✔ |
| yarn | npm | ✔ | ✔ |
| yarn | pnpm | ❌ | ✔ |
| yarn | bun | ❌ | ✔ |
| pnpm | npm | ❌ | ❌ |
| pnpm | yarn | ❌ | ❌ |
| pnpm | bun | ❌ | ❌ |
| bun | npm | ❌ | ❌ |
| bun | yarn | ❌ | ❌ |
| bun | pnpm | ❌ | ❌ |
Closes #40
i was actually thinking about this, and i think this should be done differently
currently we are trying to force conversion from any to any by creating distinct transformers between commands. what i should have done when i added support for (pnpm) transformers is to split it to 2 step process:
- parse command to internal model
- write it to desired format
this would make it supper easy to support a lot of different package managers