Oleh

> Thanks for report. The first test looks a bit weird. Where do the errors even happen? If the page would not load the localhost, your code in request handler...

> Note that you are not awaiting the `crawler.addRequests([next.value])` call, that's another problem in the repro. I've tried awaiting it as well but this does not change the result.

@B4nan I've updated repo to await `crawler.addRequests` calls. Data in `SDK_SESSION_POOL_STATE.json` still differs from manually collected session usage stats.

I have fixed this localy using declaration merging. Hope this helps someone.  ```typescript declare namespace chrome { /// export namespace runtime { export const onMessage: events.Event< ( message: any,...

@mp3por temp solution described [here ](https://github.com/GoogleChrome/chrome-types/issues/50#issuecomment-1954237256) UPD: I haven't noticed that you referencing Promise based version. So this one is correct, there's also overload with callback version. 

@mp3por Sorry, I didn't explain clearly. So if you don't need/want to use Promise version of `sendMessage` you have two options: 1. Explicitly pull desired type from provided type definitions...

@Toumash this happens because webpack tries to fetch hot update from the url opened in tab, you can change that by changing publicPath on devserver to be something like `https://192.168.0.101:${port}`...