Skip to content
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

fix(docs): yarn1 does not need -W flag #10419

Merged
merged 1 commit into from Jun 2, 2022
Merged

fix(docs): yarn1 does not need -W flag #10419

merged 1 commit into from Jun 2, 2022

Conversation

Zamiell
Copy link
Contributor

@Zamiell Zamiell commented May 22, 2022

I tried omitting the flag and everything seemed to work fine with yarn1.
if yarn2 needs this, it should be clarified which version that it is talking about.

(furthermore, it is unclear what the -W flag would even do. would it mutate the package.json in a special way, or install the deps in a special way? if the latter, then someone cloning the monorepo from scratch would have failures when doing their initial yarn invocation, so this doesn't make much sense.)

I tried omitting the flag and everything seemed to work fine.
if yarn2 needs this, it should be clarified which version  that it is talking about
@nx-cloud
Copy link

nx-cloud bot commented May 22, 2022

@vercel
Copy link

vercel bot commented May 22, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated
nx-dev ⬜️ Ignored (Inspect) May 22, 2022 at 4:06AM (UTC)

@bulldog98
Copy link
Contributor

yarn2 and 3 do not have the -W flag and the command fails altogether

@bcabanes bcabanes changed the title fix(docs) yarn1 does not need -W flag fix(docs): yarn1 does not need -W flag Jun 2, 2022
@bcabanes bcabanes merged commit a7e2d0c into nrwl:master Jun 2, 2022
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants