Sergey Zarovskiy

:+1: Thanks @vproman for mentioning working commit number, saved me some time.

Same problem: https://indigo-ui.github.io/speedtracker/?period=month

https://github.com/apache/cordova-plugin-inappbrowser/issues/965 likely the reason why it works how it works

This PR looks good. I guess you shouldn't include package-lock.json & need to address that failing test.

You can access socket like this ```js request .get('http://bla.bla') .use(function (agent) { agent.on('request', ({req}) => { req.on('socket', (socket) => { socket.on('secureConnect', () => { //... }); }); }); }) .then(/*...*/);...

@DanielJackson-Oslo this is pretty cool, can you share your solution (even if it is super hacky :))

+1 for this. With https://reactjs.org/blog/2020/08/10/react-v17-rc.html it doesn't look like this change will cause any breaking problems and what express-react-views are doing will still be compatible with react 17. I can...

Does anyone monitor these issues?

@PatrickLehnerXI what happens if you run `where npx`?

@PatrickLehnerXI that is because it updates C:\Users\patrick.lehner\AppData\Roaming\npm\npx & not C:\Program Files\nodejs\npx . It is a bit annoying, but there must be a way to fix that.