Skip to content

Incompatibility with yarn v3 #22048

Closed

Description

@sawa-ko

Which @angular/* package(s) are the source of the bug?

Don't known / other

Is this a regression?

Yes

Description

When I try to use the "ng add" tool in any package I get that error always in yarn v3.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

PS app> ng add apollo-angular
ℹ Using package manager: yarn
✔ Found compatible package version: apollo-angular@2.6.0.
✔ Package information loaded.
 
The package apollo-angular@2.6.0 will be installed and executed.
Would you like to proceed? Yes
Unknown Syntax Error: Command not found; did you mean one of:

  0. yarn add [--json] [-E,--exact] [-T,--tilde] [-C,--caret] [-D,--dev] [-P,--peer] [-O,--optional] [--prefer-dev] [-i,--interactive] [--cached] [--mode #0] ...
  1. yarn add [--json] [-E,--exact] [-T,--tilde] [-C,--caret] [-D,--dev] [-P,--peer] [-O,--optional] [--prefer-dev] [-i,--interactive] [--cached] [--mode #0] ...

While running add apollo-angular@2.6.0 --silent
✖ Package install failed, see above.

Please provide the environment you discovered this bug in

Angular CLI: 12.2.7
Node: 16.11.0 (Unsupported)
Package Manager: yarn 3.0.2
OS: win32 x64

Angular: 12.2.8
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.7
@angular-devkit/build-angular   12.2.7
@angular-devkit/core            12.2.7
@angular-devkit/schematics      12.2.7
@angular/cdk                    12.2.12
@angular/cli                    12.2.7
@angular/flex-layout            12.0.0-beta.35
@angular/localize               12.2.12
@schematics/angular             12.2.7
rxjs                            6.6.7
typescript                      4.3.5

Anything else?

I think it is the same with yarn v2 as the --silent flag no longer exists since yarn v2.

Activity

  1. clydin commented on Nov 1, 2021

    @clydin
    Member

    Can you try manually running yarn add apollo-angular@2.6.0 --silent to see if that command successfully completes?

  2. sawa-ko commented on Nov 1, 2021

    @sawa-ko
    Author

    @clydin same error

    image

  3. added this to the needsTriage milestone on Nov 4, 2021
  4. alan-agius4 commented on Nov 4, 2021

    @alan-agius4
    Collaborator

    Looks like the silent option was removed from Yarn in version 2.

    yarnpkg/berry#3542

  5. modified the milestones: needsTriage, Backlog on Nov 4, 2021
  6. AStoker commented on Apr 8, 2022

    @AStoker

    Anybody else having this difficulty? New to Angular here, set up a project to use Yarn, set Yarn to use berry (3.2.0), and now nothing works. Trying to run ng serve gives an error like this

    Could not find the '@angular-devkit/build-angular:dev-server' builder's node package.

  7. Lonli-Lokli commented on May 20, 2022

    @Lonli-Lokli

    Why it not fixed?

  8. Lonli-Lokli commented on May 20, 2022

    @Lonli-Lokli

    @alan-agius4 is there any way for Yarn users to run migrations during 13 -> 14?

  9. alan-agius4 commented on May 20, 2022

    @alan-agius4
    Collaborator

    There are a couple of workarounds for Yarn 3 users when it comes to ng update.

    • Downgrade to an older version of Yarn 1 or 2.
    • Post installation failure run ran yarn manually and invoke ng update with the --migrate-only option.
    ng update @angular/cli --migrate-only --from=13 --to=14
    ng update @angular/core --migrate-only --from=13 --to=14
    

    Yarn removed the --silent and --ignore-scripts options from their CLI in Yarn v3 which is causing some incompatibility issues.

  10. Lonli-Lokli commented on May 20, 2022

    @Lonli-Lokli

    Unfortunately following steps leads to error

    npx ng update @angular/cli --next
    yarn
    -- commit changes --
    npx ng update @angular/cli --migrate-only --from=13 --to=14 // <- FAIL
    

    Traceback

    $ npx ng update @angular/cli --migrate-only --from=13 --to=14
    DEPRECATED: The 'defaultProject' workspace option has been deprecated. The project to use will be determined from the current working directory.
    The installed Angular CLI version is outdated.
    Installing a temporary Angular CLI versioned 13.3.6 to perform the update.
    ✔ Packages successfully installed.
    Using package manager: 'yarn'
    Collecting installed dependencies...
    Found 82 dependencies.
    ** Executing migrations of package '@angular/cli' **
    
    > Remove 'defaultProject' option from workspace configuration.
      The project to use will be determined from the current working directory.
    × Migration failed: this.tree.readText is not a function
    

    I've also tries to revert changes from angular.json before this tep but result was the same.
    Also I tried to modify command to include --next ( npx ng update @angular/cli --migrate-only --from=13 --to=14 --next ) and it fails with same Update Angular packages 'dependencies' and 'devDependencies' version prefix to '^' instead of '~'. ⠋ Installing packages (yarn)...Unknown Syntax Error: Command not found; did you mean one of:

  11. Lonli-Lokli commented on Jun 2, 2022

    @Lonli-Lokli

    @alan-agius4 @clydin I've just tried to update with Yarn3 to Ng14, got this

    PS cv-ui> npx ng update @angular/core@14 @angular/cli@14 --force
    The installed Angular CLI version is outdated.
    Installing a temporary Angular CLI versioned 14.0.0 to perform the update.
    ✔ Package successfully installed.
    DEPRECATED: The 'defaultProject' workspace option has been deprecated. The project to use will be determined from the current working directory.
    Using package manager: yarn
    Collecting installed dependencies...
    Found 81 dependencies.
    Fetching dependency metadata from registry...
                      Package "jest-preset-angular" has an incompatible peer dependency to "@angular-devkit/build-angular" (requires ">=0.1102.19 <14.0.0", would install "14.0.0").
                      Package "@angular-eslint/schematics" has an incompatible peer dependency to "@angular/cli" (requires ">= 13.0.0 < 14.0.0", would install "14.0.0").
        Updating package.json with dependency @angular-devkit/build-angular @ "14.0.0" (was "13.3.2")...
        Updating package.json with dependency @angular/cli @ "14.0.0" (was "13.3.2")...
        Updating package.json with dependency @angular/compiler-cli @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/language-service @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency typescript @ "4.7.2" (was "4.5.2")...
        Updating package.json with dependency @angular/animations @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/common @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/compiler @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/core @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/forms @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/platform-browser @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/platform-browser-dynamic @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/router @ "14.0.0" (was "13.3.10")...
        Updating package.json with dependency @angular/service-worker @ "14.0.0" (was "13.3.10")...
    UPDATE package.json (4422 bytes)
    ✖ Packages installation failed, see above.
    

    And that's all :) I think it's related to Yaarn3, mb it make sense to reopen this story?

  12. angular-automatic-lock-bot commented on Jul 3, 2022

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  13. locked and limited conversation to collaborators on Jul 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions