Pre-release with Node 10 compatibility available

A pre-release version of the library has been published under the @next tag on npm. You can look at the commit history for the next branch to see what changes are included – https://github.com/ldapjs/node-ldapjs/compare/master...next

Notably, this release includes support for Node >= 10. Going forward, Node 10.16.0 will the minimally supported version. I do not believe there are any changes that strictly preclude Node 8, but it is not included in the automatic test suite. Node 8 will be desupported by year end, and is currently in “maintenance LTS.” Given this, I do not see a need to focus on supporting it when the final release version of the next branch could take just as long to be released.

There will be regular “pre” releases published as work progresses, but there is not a hard target date for the final release. You can consider these pre releases as “mostly stable.” The goal with v2.0.0 is not to radically change the outward functionality of the library. The goal is to incorporate long outstanding fixes and generally make the code easier for contributors to work with.

Please give these a releases a try by installing via npm install ldapjs@next. Please report issues you discover at https://github.com/ldapjs/node-ldapjs/issues

[jsumners]

Hmm. It looks like Debian has backported the 10.16 patches into their 10.15 version. That’s annoying.

https://metadata.ftp-master.debian.org/changelogs//main/n/nodejs/nodejs_10.15.2~dfsg-2_changelog

Mon, 08 Apr 2019 15:06:40 +0200

nodejs (10.15.2~dfsg-1) unstable; urgency=high

• New upstream version 10.15.2~dfsg Slowloris HTTP Denial of Service with keep-alive (CVE-2019-5737)

[xPaw]

We can’t.

[3/5] Fetching packages...
error ldapjs@2.0.0-pre.1: The engine "node" is incompatible with this module. Expected version ">=10.16.0". Got "8.10.0"

Telling users to use --ignore-engines isn’t a great idea.