Closed erickwilder closed 6 years ago
@vitalets - Is this project still alive?
@erickwilder thanks for the PR.
Let's ping collaborators: @sazo @beradrian are you still have time to maintain checklist-model?
@sazo @beradrian @vitalets
Can we move on with this PR? If you don't have enough time to maintain it I suggest adding a disclaimer on the main project README
about it.
Hi @erickwilder !
Agree, I will merge it. Btw, shouldn't we restrict upper angular version?
I don't think it's necessary. I'm still using the library with latest AngularJS (1.6) series and the newer (Angular 2+) don't share the same package name on npm
AngularJS is now a
peerDependency
and it has to be installed separately. This is a breaking change, so thepackage.json
version was bumped to a1.0.0
.Rationale
The default NPM dependency resolution usually works just fine with the explicit dependency, but it also introduce some weird behaviors, like allowing two versions of the same library to co-exist. Since it is generally a bad idea to have two concurrent AngularJS versions installed, turning it into a
peerDependency
makes more sense and give the user of this library all control over AngularJS installation.https://nodejs.org/en/blog/npm/peer-dependencies/