Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pre-release with Node 10 compatibility available

See original GitHub issue

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 –

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

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:12 (12 by maintainers)

github_iconTop GitHub Comments

jsumnerscommented, Sep 8, 2019

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

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)
xPawcommented, Sep 4, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

What is the convention for versioning npm packages prior to ...
A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its ...
Read more >
Previous Releases - Node.js
Version Date V8 npm NODE_MODULE_VERSION Node.js 19.3.0 2022‑12‑14 9.2.0 111 Downloads C... Node.js 19.2.0 2022‑11‑29 8.19.3 111 Downloads C... Node.js 19.1.0 2022‑11‑14 8.19.3...
Read more >
The semver parser for node (the one npm uses) - GitHub
Prints valid versions sorted by SemVer precedence Options: -r --range <range> Print versions that match the specified range. -i --increment [<level>] Increment ...
Read more >
semver - npm Docs
Always include prerelease versions in range matching. -c --coerce. Coerce a string into SemVer if possible. (does not imply --loose).
Read more >
Semantic Versioning 2.0.0 | Semantic Versioning
PATCH version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found