openMF / digital-bank-ui

Digital Bank user interface for staff on top of Fineract CN
Mozilla Public License 2.0
18 stars 28 forks source link

fix(deps): update dependency @asymmetrik/ngx-leaflet to v3.1.0 #54

Open renovate[bot] opened 3 years ago

renovate[bot] commented 3 years ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@asymmetrik/ngx-leaflet 3.0.1 -> 3.1.0 age adoption passing confidence

Release Notes

bluehalo/ngx-leaflet (@​asymmetrik/ngx-leaflet) ### [`v3.1.0`](https://togithub.com/bluehalo/ngx-leaflet/blob/HEAD/CHANGES.md#310) [Compare Source](https://togithub.com/bluehalo/ngx-leaflet/compare/3.0.2...3.1.0) Added [map events](#map-events), [layer events](#layer-events). Added several input bound map options including `[leafletMaxBounds]`, `[leafletMaxZoom]`, and `[leafletMinZoom]`. Added output binding for map center - `(leafletMapCenter)` and map zoom - `(leafletMapZoom)`. ### [`v3.0.2`](https://togithub.com/bluehalo/ngx-leaflet/compare/3.0.1...3.0.2) [Compare Source](https://togithub.com/bluehalo/ngx-leaflet/compare/3.0.1...3.0.2)

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.



This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] commented 1 year ago

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

β™» Renovate will retry this branch, including artifacts, only when one of the following happens:

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ngrx/core@1.2.0
npm ERR! Found: rxjs@6.5.4
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"6.5.4" from the root project
npm ERR!   rxjs@"6.5.4" from @angular-devkit/schematics@9.1.7
npm ERR!   node_modules/@angular-devkit/schematics
npm ERR!     @angular-devkit/schematics@"9.1.7" from @angular/cli@9.1.7
npm ERR!     node_modules/@angular/cli
npm ERR!       dev @angular/cli@"^9.0.4" from the root project
npm ERR!     @angular-devkit/schematics@"9.1.7" from @schematics/angular@9.1.7
npm ERR!     node_modules/@schematics/angular
npm ERR!       @schematics/angular@"9.1.7" from @angular/cli@9.1.7
npm ERR!       node_modules/@angular/cli
npm ERR!         dev @angular/cli@"^9.0.4" from the root project
npm ERR!     1 more (@schematics/update)
npm ERR!   20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR! node_modules/@ngrx/core
npm ERR!   @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rxjs@5.5.12
npm ERR! node_modules/rxjs
npm ERR!   peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR!   node_modules/@ngrx/core
npm ERR!     @ngrx/core@"^1.2.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.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-11T03_53_50_071Z-debug-0.log