Bug 36682 - Replace yarn with pnpm
Summary: Replace yarn with pnpm
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Paul Derscheid
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-24 14:22 UTC by Paul Derscheid
Modified: 2024-10-13 18:31 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Derscheid 2024-04-24 14:22:58 UTC
The idea is to deprecate yarn in favor of pnpm as it offers
- better disk space efficiency
- speed (compared to yarn)
- deterministic installs
- stricter dependency isolation
Comment 1 David Cook 2024-08-30 00:49:57 UTC
Sounds interesting.

It looks like we use the Debian packaged "yarn" atm, but there is no package for "pnpm". 

Guessing that's part of why we're on yarn 1.x and not yarn 2.x as well...
Comment 2 David Cook 2024-08-30 01:01:20 UTC
Also, if it stores the modules somewhere than in ./node_modules, then maybe I wouldn't have to chronically be typing "grep --exclude-dir=node_modules" haha.
Comment 3 Victor Grousset/tuxayo 2024-10-13 18:31:43 UTC
Updating Yarn and using the Yarn PnP strategy (default for new projects) doesn't look bad either:
https://github.com/pnpm/pnpm?tab=readme-ov-file#benchmark
https://yarnpkg.com/features/pnp
https://yarnpkg.com/blog/release/4.0#performances

Ultimately both are fast and well maintained.

So whichever someone motivated to attempt to make it happen finds easier to migrate to or find differentiating features for our daily use.

Thanks for opening the topic! :)