Prerequisites
Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
- What is your product version? 11.0.1
- What is your product type (Angular or MVC)? Angular
- What is product framework type (.net framework or .net core)? .net core
We are following the getting started guide and specifically the "Angular Application" - https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Getting-Started-Angular
We run:
yarn install
npm run create-dynamic-bundles
npm start
The application then appears to run successfully. However in the yarn output there are a lot of warning messages.
We are concerned about the incorrect peer dependency and has unmet peer dependency warnings:
C:\Users\Foo\source\repos\CompassZero\angular>yarn
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > [email protected]" has incorrect peer dependency "@angular/common@^12.2.8".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^12.2.8".
warning " > [email protected]" has incorrect peer dependency "@angular/common@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/animations@^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/common@^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/forms@^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/common@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/common@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/core@^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/common@^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/forms@^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0".
warning " > [email protected]" has incorrect peer dependency "@angular/compiler@>=2.3.1 <13.0.0 || ^12.0.0-next || ^12.1.0-next || ^12.2.0-next".
warning " > [email protected]" has incorrect peer dependency "@angular/core@>=2.3.1 <13.0.0 || ^12.0.0-next || ^12.1.0-next || ^12.2.0-next".
warning " > [email protected]" has unmet peer dependency "postcss@^8.0.0".
warning " > [email protected]" has unmet peer dependency "postcss@^8.0.0".
[4/4] Building fresh packages...
Done in 333.50s.
C:\Users\Foo\source\repos\CompassZero\angular>yarn
yarn install v1.22.17
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.54s.
C:\Users\Foo\source\repos\CompassZero\angular>npm run create-dynamic-bundles
> [email protected] create-dynamic-bundles
> gulp buildDev
[18:05:59] Using gulpfile ~\source\repos\CompassZero\angular\gulpfile.js
[18:05:59] Starting 'buildDev'...
Dynamic bundles are being created.
[18:06:29] Finished 'buildDev' after 30 s
We have also tried the process upgrading yarn to yarn berry and we get a similar sort of warning:
...snip...
bp-zero-template@workspace:. provides @angular/common (p5cf3e) with version 13.1.0, which doesn't satisfy what abp-ng2-module requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/common (pc58cc) with version 13.1.0, which doesn't satisfy what angular-gridster2 requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/common (p189b8) with version 13.1.0, which doesn't satisfy what ngx-captcha requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/common (pda558) with version 13.1.0, which doesn't satisfy what ngx-spinner requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/compiler (p58125) with version 13.1.0, which doesn't satisfy what codelyzer requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/core (p360b3) with version 13.1.0, which doesn't satisfy what abp-ng2-module requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/core (p787b9) with version 13.1.0, which doesn't satisfy what angular-gridster2 requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/core (pffcb2) with version 13.1.0, which doesn't satisfy what codelyzer requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/core (p92760) with version 13.1.0, which doesn't satisfy what ngx-captcha requests
➤ YN0060: │ abp-zero-template@workspace:. provides @angular/core (p3f245) with version 13.1.0, which doesn't satisfy what ngx-spinner requests
➤ YN0002: │ abp-zero-template@workspace:. doesn't provide postcss (pa4014), requested by gulp-postcss
➤ YN0002: │ abp-zero-template@workspace:. doesn't provide postcss (pc0240), requested by postcss-url
➤ YN0060: │ abp-zero-template@workspace:. provides primeicons (p2abcd) with version 4.1.0, which doesn't satisfy what primeng requests
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
...snip...
Please can you provide any guidance on whether we need to resolve these warnings and how we might do that?
We have tried to self-help with Google searches and searches of this forum - but not found anything that seems to answer the queries?
Many thanks in advance!
3 Answer(s)
-
0
Hi @commtech
These warning should not cause any kind of issue. Your project should be work as expected when you use yarn berry. Is your project works as expected?
-
0
Hi
Thank you for the response. We have only just started looking at Zero and the initial load of the application does indeed seem to opertate correctly.
We were just concerned that at such an early step in the process we already have a screen full of warnings.
I really wanted to understand if this was to be expected with this release - and its nothing to worry about - or whether there is a problem with my development comp.
Looking at the package files I can see why the issues are arising - is this not something the Zero team have seen or encountered?
I appreciate this may be nothing to be concerned about - if so? perhaps a little note on the getting started documentation?
We just wanted to make sure we are staring off with a solid and correct foundation!
Thanks
warning " > [email protected]" has incorrect peer dependency "@angular/common@^12.2.8". <-- Issue
angular/package.json example: "@angular/common": "^13.1.0", "abp-ng2-module": "^6.4.0"
angular/node_modules/@angular/common/package.json "name": "@angular/common", "version": "13.1.0",
angular/node_modules/abp-ng2-module/package.json "name": "abp-ng2-module", "version": "6.4.0", ...snip... "peerDependencies": { "@angular/common": "^12.2.8", <-- Issue
-
0
Hi @commtech
abp-ng2-module is compatible with Angular 13 but it is not updated yet. There is nothing to worry, you can safely develop your app and ignore those warnings.
We will update abp-ng2-module to Angular 13 in the next release so you can easily update it.
Maybe adding a notice to the getting started docs will help, we will consider this, thank you.