-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Which Package Manager should I use? #785
Comments
Something interesting I found out about yarn 3 (2+ too I guess) is the local cache feature. It allows to keep the cache across Example with a github action and restore_key (but the same apply locally or with docker/bildkit) - name: Get yarn cache directory path
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn config get cacheFolder)"
- name: Restore yarn cache
uses: actions/cache@v2
id: yarn-cache
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: yarn-cache-folder-${{ hashFiles('**/yarn.lock', '.yarnrc.yml') }}
restore-keys: |
yarn-cache-folder- When installing a new dependency, ie: superjson, there's no need to invalidate the whole thing.
See also actions/setup-node#325 On Vercel, the following hack generally works Worthy to share. |
I tried pnpm before transitioning to npm workspaces, as prisma and next misbehaved with package hoisting |
…rcel (#3480) <!-- PR title: GRW-123 / Feature / Awesome new thing --> ## Describe your changes Move yarn cache outside node_modules, see vercel/turborepo#785 <!-- What changes are made? If there are many changes, a list might be a good format. If it makes sense, add screenshots and/or screen recordings here. --> ## Justify why they are needed ## Checklist before requesting a review - [ ] I have performed a self-review of my code
Add page in documentation about
yarn
vs.yarn
2+ vs.pnpm
vs.npm
. Compare features:Dimensions
turbo
The text was updated successfully, but these errors were encountered: