ngx-daterangepicker-material resumes releases after a gap of more than three years

The versioning scheme is the design decision. The package major now equals the Angular major: v16 works with Angular 16, v17 with Angular 17, and so on up to v22 ^[6]. In our view that is a sound trade for a UI library. The version number tells you which framework it was built against, and the cost is that every Angular upgrade becomes a library upgrade.

The upgrade method is worth reading closely. `ng update` only moves one major at a time, so the maintainer went through each one ^[7]. Each step followed the same routine: build the library, pack it and install it into a new Angular app, then open a real browser and confirm that selecting a date updates the value ^[8]. That last check found bugs the maintainer's own build never showed, because a fresh app does not have the same config as the repo ^[9].

The lapse had an ordinary cause. According to the maintainer's post, there was no big drama: at first there was simply no time for a few months, and new issues kept coming ^[21]. The maintainer wrote: "When I came back, the list was long, and every issue felt like a small debt." ^[20] Then CI broke. The build failed on a clean checkout, the tests did not start in a modern Chrome, and the demo deploy failed ^[4]. This year the maintainer fixed build, tests, CI and demo deploy before touching the issue list ^[5].

The post gives the last old release as October 2022 and the next one only as "2026". It does not name the month. The gap is therefore between 39 and 50 months ^[24].

The results are the maintainer's own numbers. The library had almost no tests before and has about 140 now ^[13]. Open issues fell from close to 200 ^[3] to about 13 ^[14], a drop of roughly 93 percent if 200 is the starting count ^[25]. The post is the only source for those counts.

Adopting it costs little, and the costs are specific. The picker's value is `{ startDate, endDate }` as dayjs dates, so your form model holds dayjs objects ^[22]. The library does not depend on `@angular/material`. It only looks like it ^[18]. The maintainer's case against Material's own picker is that it has no predefined ranges, no time on a range, and uses two inputs ^[19]. For the old complaint about a calendar clipped inside `mat-form-field`, the post offers `[appendToBody]="true"` ^[12]. To pin the Angular 22 build, the post gives `npm install ngx-daterangepicker-material@22` ^[23].