-
Notifications
You must be signed in to change notification settings - Fork 41
v17 #138
Comments
It's numbers are relatively low, but it's still being installed and used. |
I can take a shot at upgrading it to v17 and then I can look at maintenance later. Anything I need to adhere to @hueniverse? |
@sfabriece just the normal hapi.js code style rules. |
I'm going to deprecate tv is no one steps forward to take over it by the end of the week. |
@hueniverse I'll take over for it. I would like to use it on a current project and I'd prefer to use v17 for it so I'll be updating it regardless. |
@Kevnz Great. Go ahead and prepare a PR and once it's ready, I'll get you the access rights. |
@Kevnz how is progress going on the update to support v17? If you need help let me know, I'd been keen to lend a hand in moving this forward. |
@rossanthony thanks, I've been working on the upgrade as I work on another project. Basically my idea is to get an MVP working on v17, using as much as possible from what is already in the project. Then a version after that the brings the front end up to newer frameworks/standards. Happy to talk further, feel free to message me in the hapi slack https://hapihour.slack.com/ Join here |
Progress? |
Any updates on this? This is a useful tool. Would like to see @theRemix's PR get merged. |
Anyone using this? This module is not maintained to hapi.js standards given how many issues are still open over multiple years. Either we find someone to take care of it and migrate it to hapi v17 or we deprecate it.
The text was updated successfully, but these errors were encountered: