microsoft / applicationinsights-angularplugin-js

MIT License
32 stars 19 forks source link

Add support for Angular v12 #23

Closed drielnox closed 3 years ago

drielnox commented 3 years ago

Installing this package on Angular v12, npm throws me this:

PS C:\Users\developer\Documents\a_folder> npm i --save @microsoft/applicationinsights-angularplugin-js 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: a_project@0.0.0
npm ERR! Found: @angular/common@12.0.5
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~12.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^11.0.6" from @microsoft/applicationinsights-angularplugin-js@2.6.3
npm ERR! node_modules/@microsoft/applicationinsights-angularplugin-js
npm ERR!   @microsoft/applicationinsights-angularplugin-js@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\developer\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\developer\AppData\Local\npm-cache\_logs\2021-06-23T17_38_03_592Z-debug.log
abisleem commented 3 years ago

Any updates on this? I'm facing a similar issue but with @angular/common@10.2.5

drielnox commented 3 years ago

@xiao-lix Do you know when they are going to release the new version with the fix? I ask this, because I have an item in the backlog of my company's project that is blocked for this reason.

xiao-lix commented 3 years ago

@drielnox hi , just released 2.6.4 version. Please test it out. Thanks.

drielnox commented 3 years ago

@xiao-lix It still doesn't work.

PS C:\Users\developer\Source\a_folder> npm install @microsoft/applicationinsights-angularplugin-js
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: a_project@0.0.0
npm ERR! Found: @angular/common@12.1.5
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~12.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^11.0.6" from @microsoft/applicationinsights-angularplugin-js@2.6.4
npm ERR! node_modules/@microsoft/applicationinsights-angularplugin-js
npm ERR!   @microsoft/applicationinsights-angularplugin-js@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\developer\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\developer\AppData\Local\npm-cache\_logs\2021-08-17T18_21_05_491Z-debug.log
danielloynaz commented 3 years ago

Hi @xiao-lix, @angular/common was upgraded to 11.0.6. Angular 12 is not supported, it should be @angular/common@ ^12.x.x

$ npm install @microsoft/applicationinsights-angularplugin-js npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: angular12-ui@1.0.0 npm ERR! Found: @angular/common@12.2.13 npm ERR! node_modules/@angular/common npm ERR! @angular/common@"~12.2.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @angular/common@"^11.0.6" from @microsoft/applicationinsights-angularplugin-js@2.6.4 npm ERR! node_modules/@microsoft/applicationinsights-angularplugin-js npm ERR! @microsoft/applicationinsights-angularplugin-js@"*" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.