4 ms·

Good news, I just looked at that bug again and it turns out it's no longer reproducible in the latest version of npm.