Perf issue: npm/yarn download all platform builds! #2949
Comments
|
|
|
This was a bug with Yarn: yarnpkg/berry#3317. It was fixed in 2021: yarnpkg/berry#3575. You need to use a newer version of Yarn to pick up the fix. |
|
Unfortunately, I still don't use Berry! And I don't have enough time budget for updating right now. Thanks for the quick response. It's amazing to me that you still have enough time to support and answer questions despite your huge workload. Please, if you get a chance, teach us some tips in the form of a simple article 😄 |
8 tasks
kodiakhq bot
pushed a commit
to vercel/vercel
that referenced
this issue
Feb 8, 2024
…d from `yarn` to `npm` (gated behind feature flag) (#11131) This PR changes the default package manager from `yarn` to `npm` in the case that no lockfile is present. Many years ago when `yarn` was first released, it was much faster than `npm` so we used it by default. That is no longer the case today and `yarn@1` is no longer receiving new features. For example, `sharp` and `esbuild` no longer works with `yarn@1`: ### Related - lovell/sharp#3750 - evanw/esbuild#2949 Note that this change will not impact most projects because most used a lockfile.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @evanw, thanks to make and publish this great tools.
I have to wait a long time to download all the platform builds every week to update esbuild!
Is there a way to solve this problem?
Thank you in advance.
The text was updated successfully, but these errors were encountered: