Tracking: Revert #5102 when possible

[jasnell]

PR #5102 was landed as a temporary measure to get npm in master working again. This issue is intended to serve as a reminder that it needs to be reverted as planned.

/cc @ChALkeR @thealphanerd @nodejs/ctc

[thefourtheye]

Can we revert after the next npm release or we are going to wait till the major release?

[bnoordhuis]

The plan is to release in v6 and remove again in v7 to give people time to upgrade their dependencies.

[ChALkeR]

@jasnell npm is not the sole user of graceful-fs (and there might be other libs that do the same), my proposal was to keep this in 6.x branch and revert in master as soon as 6.x is branched.

[MylesBorins]

@ChALkeR do you know how many modules rely on the pre fix version?

[ChALkeR]

@thealphanerd Uh-oh. Not yet. For now, I can check only direct dependants.
Data from 2016-01-28, all direct dependants of graceful-fs: https://gist.github.com/ChALkeR/e51abea04b6facfb9bd0.

Note that v4.x are fixed, v3.x and below are affected, so I excluded everything that works with 4.x.

Update: less is fixed in current master, but no release has been published yet, less@2.6.0 still depends on graceful-fs v3.

[ChALkeR]

@thealphanerd I will check indirect deps too, but I can't say when yet.