We should really update npm soon, as we get a lot of bug reports for that old version lately.

Edit 2018-06-18:

Do not npm install ftpd

… unless you specifically need the old (but stable) version, e.g. due to windows support concerns.

(Edit 2019-11-22: see update below)

How to install the latest version

Lots of people will probably want to install the repo version instead:

npm install https://github.com/nodeftpd/nodeftpd/

The result should look somewhat like this:

npm WARN [… several warnings …]
 
+ ftpd@0.2.14
added 3 packages in 11.261s

Make sure to check the version which version npm reports it has installed (the "plus" line). It should be

version 0.2.14 or later.

Update 2019-11-22: … FROM THIS repo.

because now npm has ftpd and nodeftpd packages with higher version numbers. Those are not supported here.

When I contacted npm support about how we could help people discover that there's a newer version outside of npm, they nonetheless suggested a package name dispute. While imo that's one of the worst strategies I could think of (I won't even call that a "solution"), there's a real chance that npm won't build a new tool when they consider their hammer as a (in their view) solution.

So in case npm doesn't (soon) manage to help people discover packages outside of npm, should we try and update npm with some sidetrack-versioned patch that annotates the readme? (Obvious next question in another comment for independent 👍 / 👎 voting.)

In case previous question is favored and @sstur can't find time to decide: Should I try and appropriate the package name "ftpd" in order to update the readme?