Closed hfhchan-plb closed 3 weeks ago
The newest @nestjs/cli (10.4.5) depends on:
"@angular-devkit/core" "17.3.8" "@angular-devkit/schematics" "17.3.8" "@angular-devkit/schematics-cli" "17.3.8"
while the newest @nestjs/schematics (10.2.3) depends on:
"@angular-devkit/core" "17.3.11" "@angular-devkit/schematics" "17.3.11"
The deps version should be synced between @nestjs/schematics and @nestjs/cli, or a version range should be used instead:
"@angular-devkit/core" "^17.3.8" "@angular-devkit/schematics" "^17.3.8" "@angular-devkit/schematics-cli" "^17.3.8"
No response
Avoiding too many deps in yarn.lock
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The newest @nestjs/cli (10.4.5) depends on:
while the newest @nestjs/schematics (10.2.3) depends on:
Describe the solution you'd like
The deps version should be synced between @nestjs/schematics and @nestjs/cli, or a version range should be used instead:
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Avoiding too many deps in yarn.lock