1
Fork 0

Switch to PNPM

This commit is contained in:
KorbsStudio 2023-02-27 03:30:51 -05:00
parent 4a87d24466
commit 5f1313d314
No known key found for this signature in database
2 changed files with 4869 additions and 2 deletions

View file

@ -21,20 +21,24 @@ ___
## Package Managers
Korbs Studio is currently looking other package managers to see which one is more or less efficient.
Final Choice: Korbs Studio has decided to use **PNPM** as it is techincally more space efficient when working with multiple projects and much faster in a lot of cases.
**Benchmark**
Speed:
- NPM - 1M 21S
- Yarn v1 - 53S
- Yarn Berry - 21S
- Yarn Canary - 18S
- PNPM - 44S
- PNPM - 32S (Can vary - Could be 3M if you're using PNPM for first time)
Disk Space:
- NPM - 28,099 items, totalling 591.9 MB
- Yarn v1 - 25,259 items, totalling 583.6 MB
- Yarn Berry - 1,230 items, totalling 510.9 MB
- Yarn Canary - 524 items, totalling 398.3 MB
- PNPM - 28,038 items, totalling 577.2 MB
- PNPM - 28,038 items, totalling 577.2 MB (33.5kb*)
> "*" The way PNPM works is by linking all node_modules folders on your drive to one folder, this way you don't have multiple node_modules folders through out your drive.
> Yarn Berry and Yarn Canary: With their Plug N Play option enabled. ElectronJS failed to launch resulting in a "path" argument issue. Astro launched with CSS not loading. Also, this adds like 4 extra files to the root directory, which I dis-encourage. Sad, it looked promisingly. The project may need some adjustments to make it all work.
___

4863
pnpm-lock.yaml Normal file

File diff suppressed because it is too large Load diff