Yarn Berry (v2 & v3) is not supported: Unsupported option name ("--no-lockfile")

Open
#741 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Start by tracing the yarn test:ember-compatibility entry point and locating where --no-lockfile is passed to Yarn. Reproduce the command with Yarn Berry, then verify that the compatibility test flow completes without the unsupported option while remaining compatible with the reported Yarn 1 behavior.

Written by the indexing model from the issue text.

Description

Hi!

When trying to run yarn test:ember-compatibility in my addon, I receive:

❯ yarn test:ember-compatibility
Unknown Syntax Error: Unsupported option name ("--no-lockfile").

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]
Error!
1
undefined

This is because Yarn Berry does not have the --no-lockfile option.

I cannot use Yarn 1 because it crashes on nohoist: *, and package hoisting in my monorepo breaks many things.

Dominant language
JavaScript
Stars
180
Forks
57
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/ember-try

All issues in ember-cli/ember-try

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.