hapipal/hodgepodge

Resolving hapi plugin dependencies since 2015

hodgepodge's Issues

Fix hodgepodge plugin attribute

The hodgepodge plugin attribute used to cause failure of plugin registration when present, which was desirable. As of some hapi version (that hodgepodge supports), this is no longer the case. Suggested,

plugin.attributes = {
    name: 'some-name',
    dependencies: { hodgepodge: true }
};

or

plugin.attributes = {
    name: 'some-name',
    dependencies: { hodgepodge: [list, of, deps] }
};

Support hapi v19

And in turn, also node v12, v14.

Switch to ad hoc maintenance

I propose we switch this module to ad hoc maintenance. Most modules in the hapi pal organization receive similar or equal treatment to each other. For example, when a new version of node or hapi is released, all modules are actively updated to remain compatible. Under "ad hoc maintenance" issues for those tasks would be created and PRs welcome, but the work wont actively be completed. When updates do occur they will be accepted if they stick with pal's standards and conventions.
This means that this module would receive looser maintenance and may not stay up to date with nodejs or hapi unless the community makes a point to keep it up to date. A note of this fact would display in the readme. The main factor leading to this decision is that this module hasn't received contributions, doesn't have any dependents, and receives very few downloads. If the module ends-up unmaintained it will likely be deprecated, and if it is maintained or becomes more popular then it could come out of ad hoc maintenance, so nothing is absolutely final here.

Update dependencies with new @hapi scope

Modules in the hapijs org now are published under the @hapi/x scope. References to these dependencies need to be updated.

Hapi v17 Support

Overview

If you are not aware yet, Hapi v17 is making the transition from callbacks to async/await, as well as deprecating some other rarely used functionality. This is a breaking change that may make your plugin no longer compatible with the Hapi API.

Changelog

Draft release notes can be found here: hapijs/hapi#3658

Target Release

The target release date for v17 is the beginning of November.

Tasks

• Reply to this to acknowledge that you are actively maintaining this module and are willing to update it
• Update plugin to be fully async/await compatible using the v17 branch from Hapi for testing

  Possible dev flow for updating

  • Clone Hapi
  • npm link within the Hapi repo
  • npm link hapi within your plugin repo
  • Your plugin will now be using v17 of Hapi branch for tests
• Release new major version of your plugin on npm. Please use a major version increment as this will be a breaking change and it would be terrible for it to sneak into current versions of Hapi.

Notes

• Support is being dropped for all versions of Node <8.0.0.
• Hapi v16 will continue to be supported for as long as there exists a Node LTS actively being supported that is not compatible with v17.
• Targeted release date is November 1st, 2017. Please try to have your plugin updated before then.
• This issue is being opened because your plugin is listed on the official hapi website

Support hapi v20