Original issue in https://github.com/sortlist/sortlist/issues/18791 and some requirements in https://docs.google.com/spreadsheets/d/1HzL-Swnh0qLOB-vLWDeHQtyJMpkCF7RvFWTaBU0U4Xo/.
On a (cached) github action. pnpm7 ±50s (244Mb store cache) / yarn4-nm ±75s (190Mb yarn install cache)
Tests made with pnpm 7+ and yarn 4.0.0rc (node-modules/pnp) based on https://github.com/belgattitude/nextjs-monorepo-example. Tests have been made in a way to evaluate CI performance. There's other perf bench: pnpm or yarn. Conclusions are pretty similar. This benchmark helped to create this yarn install composite action
Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).
Yarn 3+/4+ with nodeLinker: node-modules. (Not using yarn ? see the corresponding pnpm 7/8+ action gist)
Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).
pnpm v7 or v8 (not using pnpm ? see the corresponding yarn action gist)
| import type { Compilable, InferResult, Kysely } from 'kysely'; | |
| type QueryResultSuccess<T> = { | |
| success: true; | |
| data: T; | |
| }; | |
| type QueryResultError = { | |
| success: false; | |
| errorMsg: string; | |
| }; |