Open nick-bull opened 4 years ago
Hello @nick-bull and everyone else visiting this issue.
I've talked to Manuel (the module author) in Twitter. TL;DR: they are not looking to spend any time on this module and recommend forking.
Which I did -> https://github.com/flash-oss/node_acl
And published to npm as acl2
.
The acl2
is almost a drop-in replacement for acl
module. The only notable breaking change would be the different backend constructors interface and a default prefix. See more info here.
In addition, I pulled and applied a number of good PRs from this repository. Modernised the codebase. Fixed all the deprecation warnings. And run the module in production for few weeks (all good so far).
We plan to maintain the module for as long as possible. We welcome contributors and volunteer maintainers!
thank goodness for it !!!
Hi just found this here, are there new acl types (@types/acl) with this fork ? Like @types/acl2 or do the old types work with this package ?
Most old types would work with acl2. See README for the list of breaking changes (there is one actually).
On Fri, 11 Dec 2020, 23:02 Kryofex, notifications@github.com wrote:
Hi just found this here, are there new acl types (@types/acl) with this fork ? Like @types/acl2 or do the old types work with this package ?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/OptimalBits/node_acl/issues/285#issuecomment-743154434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMMEL6SJNP4LHGU645WIWTSUIC5TANCNFSM4K2F62NQ .
A while since the last commit, 120 issues, 24 pull requests going back to 2015... Eek, is there anybody maintaining this project, or is it just that stable? Are you looking for maintainers to help close some of those issues or PRs outstanding? @manast or any other maintainer - I'd love to know/help!