Repository navigation
Closed
Labels
area: @angular/clifreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fixyarn 2+
Milestone
Description
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.
Reacted by Andrew Stoker
Metadata
Metadata
Assignees
Labels
area: @angular/clifreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fixyarn 2+
Activity
clydin commentedon Nov 1, 2021
Can you try manually running
yarn add apollo-angular@2.6.0 --silentto see if that command successfully completes?sawa-ko commentedon Nov 1, 2021
@clydin same error
alan-agius4 commentedon Nov 4, 2021
Looks like the silent option was removed from
Yarnin version 2.yarnpkg/berry#3542
AStoker commentedon Apr 8, 2022
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 servegives an error like thisLonli-Lokli commentedon May 20, 2022
Why it not fixed?
Lonli-Lokli commentedon May 20, 2022
@alan-agius4 is there any way for Yarn users to run migrations during 13 -> 14?
alan-agius4 commentedon May 20, 2022
There are a couple of workarounds for Yarn 3 users when it comes to
ng update.yarnmanually and invokeng updatewith the--migrate-onlyoption.Yarnremoved the--silentand--ignore-scriptsoptions from their CLI in Yarn v3 which is causing some incompatibility issues.Lonli-Lokli commentedon May 20, 2022
Unfortunately following steps leads to error
Traceback
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 sameUpdate Angular packages 'dependencies' and 'devDependencies' version prefix to '^' instead of '~'. ⠋ Installing packages (yarn)...Unknown Syntax Error: Command not found; did you mean one of:Lonli-Lokli commentedon Jun 2, 2022
@alan-agius4 @clydin I've just tried to update with Yarn3 to Ng14, got this
And that's all :) I think it's related to Yaarn3, mb it make sense to reopen this story?
angular-automatic-lock-bot commentedon Jul 3, 2022
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.