@sentry/browser
@sentry/node
raven-js
raven-node
_(raven for node)_5.29.2
I'm upgrading to Angular 11 and get this warning:
npm WARN @sentry/[email protected] requires a peer of @angular/common@^10.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN @sentry/[email protected] requires a peer of @angular/core@^10.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN @sentry/[email protected] requires a peer of @angular/router@^10.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN @sentry/[email protected] requires a peer of @angular/common@^10.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN @sentry/[email protected] requires a peer of @angular/core@^10.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN @sentry/[email protected] requires a peer of @angular/router@^10.0.3 but none is installed. You must install peer dependencies yourself.
still exists in 6.0.0 (and angular 11)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^11.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^10.0.3" from @sentry/[email protected]
npm ERR! node_modules/@sentry/angular
npm ERR! @sentry/angular@"^6.0.0" 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.
Most helpful comment
still exists in 6.0.0 (and angular 11)