Lance J.

the stream.pipe function is async, which means that while its unzipping js is executing the rest of the code. If you want to execute the rest after the unzipping finished,...

yeah the function has to be async then. I recommend doing it with a callback and trying to solve that problem with require

I really need the `net.createConnection` function for my app to create an IPC connection. How much work would it be to implement that? Could someone with little/basic Rust experience implement...

> Could you explain why? There are legitimate use cases on the web suffering from your strict decision, so an explanation is required. @mounirlamouri, this question seems to have never...

async/await works inside for-loops. the problem probably lies in the code. If you ask a question it's recommended to post a code snippet with it so we can be helpful

Works perfectly fine for Node v14.15.4 LTS ```js const asyncTimeout =(timeout)=> new Promise(res => setTimeout(res, timeout)); main(); async function main() { for (let counter = 0; counter < 10; counter++)...

add a log above the `process.on('unhandledRejection', ...)` and see how often it is logged. those 11 eventlisteners have to come from somewhere

thats weird. is it possible you add that event handler somewhere else? maybe log the event-emitter with console.dir. i believe it shows the registered event handlers.

The problem here is probably that you await the result before updating your version. Therefore multiple requests could end up using the same version. Move your `setCurrentVersion(latestVersion)` above the await...

Furthermore async functions have nothing to do with java synchronized methods