Skip to content

Instantly share code, notes, and snippets.

@belgattitude

belgattitude/pnpm-vs-yarn-on-vercel.md

Last active October 10, 2022 21:29
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save belgattitude/38bc4b779d14d17793316c936879f06e to your computer and use it in GitHub Desktop.
Save belgattitude/38bc4b779d14d17793316c936879f06e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
pnpm-vs-yarn-on-vercel.md

Comparison

  • Yarn 4.0.0-rc.23: 2+ minutes (constant yarn cache is preserved between lock changes: cache saved in .next/cache/yarn)
  • Pnpm 7.13.x: 4+ mins (cold cache) / 3+ minutes (warm cache)

Deploy size

PS: add NEXT_DEBUG_FUNCTION_SIZE=1 in the vercel envs/

Lambdas sizes

Regular install

ỳarn install --immutable vs pnpm install --frozen-lockfile --strict-peer-dependencies --prefer-offline

image

image

Deployment time

Yarn

Override command: YARN_CACHE_FOLDER=./.next/cache/yarn yarn install --immutable --inline-builds

image

PNPM (default)

Override command: pnpm i --frozen-lockfile

image

PNPM (optimized)

Override command: pnpm install --frozen-lockfile --strict-peer-dependencies --no-optional --prefer-offline

Notes

Attemps that didn't work (e2e tests failed)

Install with pnpm --no-optional

ỳarn install --immutable vs pnpm install --frozen-lock-file --strict-peer-dependencies --no-optional

image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment