can't be upgraded to use `rebrowser-puppeteer-core` version 24.8.1

[aguyinmontreal]

I know this project is no longer supported, but I tried bumping it's rebrowser-puppeteer-core dependency from 23.10.3 ("^23.3.1") to the latest version (24.8.1) and it triggers an error when puppeteer does page.on("request"). Someone knows why?

[cause]: ProtocolError: Protocol error (Fetch.enable): 'Fetch.enable' wasn't found
at <instance_members_initializer> (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\common\CallbackRegistry.js:101:14)
at new Callback (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\common\CallbackRegistry.js:105:16)
at CallbackRegistry.create (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\common\CallbackRegistry.js:23:26)
at Connection._rawSend (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\Connection.js:99:26)
at CdpCDPSession.send (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\CdpSession.js:73:33)
at #applyProtocolRequestInterception (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\NetworkManager.js:188:24)
at C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\NetworkManager.js:140:20
at Array.map (<anonymous>)
at #applyToAllClients (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\NetworkManager.js:139:60)
at NetworkManager.setRequestInterception (C:\Users\abc\puppeteer-real-browser\node_modules\rebrowser-puppeteer-core\lib\cjs\puppeteer\cdp\NetworkManager.js:179:38)

[RubberArchind]

it might because the chrome version was not match with the puppeteer, try to update your chrome or use different version

[aguyinmontreal]

it might because the chrome version was not match with the puppeteer, try to update your chrome or use different version

nope, the latest Chrome is working fine with rebrowser-puppeteer-core 23.10.3. The issue is with rebrowser-puppeteer-core 24.8.1

Actually the AI tells me the following: The rebrowser patches in 24.8.1 introduce a new runtime fix system that bypasses the standard Runtime.enable approach that was causing conflicts with Fetch.enable.

[RubberArchind]

why you upgrading to 24.8.1 then? did you need some feature there?