Support Node 18

[garethbowen]

Description

medic/cht-conf#538

Code review items

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or integration tests where appropriate
• Backwards compatible: Works with existing data and configuration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[garethbowen]

Do we plan to go to Node 18 in cht-core in the near future?

Yes, in this issue ( https://github.com/medic/cht-core/issues/7993 ) which is blocked on this cht-conf change...

Can we start dropping support for unmaintained Node versions (<14) after 3.17.x is EOL?

In cht-conf we can drop support for Node versions quite aggressively, firstly because it's relatively easy to update a cht-conf environment, and secondly because it's relatively easy to install an old version of cht-conf. Soon we're going to be forced to drop some due to libraries we use (eg: webpack) so that's a good time to review the support and probably release a major version to communicate this.

In cht-core 4.x we only need to support one Node version (yay Docker!).

[medic-ci]

:tada: This PR is included in version 3.15.3 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: