It doesn't backup global npm packages?

[NightMachinery]

The program needs to run npm ls --parseable=true -g instead of just npm ls --parseable=true to list global packages.

[alichtman]

That sounds right to me. Want to open a PR? @NightMachinary

[NightMachinery]

Then what does it backup from npm?!

…

On Sat, Sep 1, 2018 at 5:27 AM Aaron Lichtman ***@***.***> wrote: That sounds right to me. Want to open a PR? @NightMachinary <https://github.com/NightMachinary> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aii--slX0HB7cpNKu7UYqAVI-A0y7A-Zks5uWduGgaJpZM4WV_SA> .

[alichtman]

Honestly, I'm not really a node developer and don't work with npm that much.

It looks like it backs up local node modules (so, goes up through the file tree until it finds a node_modules directory and backs up whatever is in that.)

That's an oversight on my part, and should be fixed.

[shobrook]

@NightMachinary Y'know.. it's open source for a reason

https://youtu.be/TviGil-U2HE?t=36s

[preetham]

Can I work on this ?

[alichtman]

Go for it, @kamidipreetham.

I think the correct fix was suggested by @NightMachinary, so try that out and see if it solves the bug.