Removed dependency on timespan

[reaktivo]

Will change the display of uptime from:
38d 16h 1m 23s
into
38:16:1:23.49

See https://nodesecurity.io/advisories/533

See #955

[dtrawins]

Is there some ETA for merging it and new release?

[bennycode]

@reaktivo: Great that you fixed forever's security issue.

It could also be fixed using Moment.js:

const moment = require('moment');
const uptime = moment.utc(new Date().getTime() - proc.ctime).format('DD:HH:mm:ss.SSS');
return proc.running ? uptime.yellow : "STOPPED".red;

[marin-liovic]

Still no ETA?

[bennycode]

It looks like that this project here is dead...

@indexzero, @mmalecki, @AvianFlu, @bmeck, do you think otherwise?

[marin-liovic]

I see @asci approved changes. So it looks like somebody is still on the project...

[asci]

I'm not the maintainer of this project :)

[bennycode]

I also approved it. ✔️

Now we need to find someone to merge it and to make a release version. 😁

Telling from npm, these are the "Magic Five" (in alphabetical order) who have the power to do it:

• @bmeck
• @indexzero
• @jcrugzz
• @jeffsu
• @julianduque

[jiafangtao]

Hello @bmeck @indexzero @jcrugzz @julianduque, do you have ETA for new release with this fix? Regards and thanks.

[roblav96]

@reaktivo @asci @bennyn I published this PR to a temporary package on npm forever-timespan-patch for the time being. Hope this all gets resolved. Thanks!

[roblav96]

npm install forever-fixed -g

npmjs.com/package/forever-fixed

@asci @dtrawins @bennyn @jiafangtao @iwwwi

Credit: @reaktivo

[kibertoad]

Let's continue the discussion here: #1014
I've explained in the description of PR why I ended up implementing a different approach instead of just merging this PR.