We fixed the build by passing an inline arrow function to chrome.devtools.inspectedWindow.eval, instead of the pre-bound method reference. The new @types/chrome 0.3 typings declare the callback as a (result, exceptionInfo) tuple union, and our explicitly typed (info?) callback was not assignable to it. With the inline arrow, TypeScript infers the parameter types from the new signature, so the TS2769 error goes away.
Failed after Rrenovate[bot]View latest
Merge 25bda7455b8fc4d6edd4aead5c9971951b0ec99e into b25d067c5294127bde11a8f14023372e03b2ff54
42683e94838Open on GitHubThis code change can't be applied
You do not have the right to apply or reject this fix, please ensure you are logged in with the correct permissions.