Remove "@angular-devkit" from custom-webpack published package.json dependencies.

“@angular-devkit/architect”: “>=0.1100.0 < 0.1200.0”, “@angular-devkit/build-angular”: “>=0.1100.0 < 0.1200.0”, “@angular-devkit/core”: “^11.0.0”

in “@angular-builders/custom-webpack” in some scenario with yarn causes that we have two different versions of these packages, one in node_modules root and another in node_modules/@angular-builders/custom-webpack/node_modules.

Moving these dependencies to peer dependencies in the published package.json can solve this problem.

[larixer]

@abadakhshan @just-jeb You might be interested to declare these dependencies as both peerDependencies and regular dependencies. In this case npm and yarn 1 will treat them as regular dependencies. Yarn 2+ will treat them as peerDependencies if they are provided by the parent package and regular dependencies if they were not provided by a parent package.

[abadakhshan]

I guess it’s a problem with yarn, not with the builders. Am I missing something?

I created an issue for Yarn https://github.com/yarnpkg/berry/issues/2482