The problem described in richtr/NoSleep.js#15 applies to react-wakelock as well, since the same method is used.
Basically the window.stop() doesn't just abort the (dummy) location change started by react-wakelock itself, but also all other HTTP requests on the same page.