Berry: yarn set version berry doesnt work

Created on 5 Feb 2020  路  8Comments  路  Source: yarnpkg/berry

Hey! Trying out yarn 2, following the docs I'm not able to create a project:

node --version

v12.14.1

npm install -g yarn@berry

yarn --version

2.0.0-rc.27

yarn set version berry

Usage Error: No project found in /Users/wesbos/Sites/projectName
$ yarn set version [--allow-rc] [--dry-run]

same errors when I pass --allow-rc or --dry-run

bug stale

Most helpful comment

When entering yarn set version berry the following error generated:
error Command "set" not found. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I am running yarn on Ubuntu 18.04.4 LTS
yarn --version : 1.21.1
node --version : 12.15.0

All 8 comments

Oh - does yarn set version berry only need to be run on yarn 1 projects? I'm starting fresh

When entering yarn set version berry the following error generated:
error Command "set" not found. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I am running yarn on Ubuntu 18.04.4 LTS
yarn --version : 1.21.1
node --version : 12.15.0

Make sure you're using Yarn 1.22 as your global binary, or use yarn policies set-version instead.

How to install V1.22.0 to UBUNTU? the official way just install V.1.21.1

@yabasha if you have npm installed you can run npm install -g yarn and it will install the latest 1.x version.

I'm getting the same error message as @yabasha and I'm using Windows.

the debian/unbuntu apt policy shows only 1.21 as the latest. No way to bootstrap without using npm per @danielleadams ...ironic :-).

Hi! 馃憢

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolution faster). It helps us help you! 馃槂

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label.

Was this page helpful?
0 / 5 - 0 ratings