Chrome Extension Manifest v3 Service Worker

[AleCucina]

I noticed there is a problem obfuscating the service worker of a manifestv3 chrome extension.
Now the function to run a script is:

    const example = "Hello World!"
    chrome.scripting.executeScript({
        func: (param) => {
            console.log(param) // Hello World!
        },
        args: [example],
        target: { tabId: tabId }
    })

But probably with the obfuscated code a problem arises because what is inside the func() loses meaning since the rest of the obfuscated code is in the service worker and not in the content of the page.

Does anyone know how to fix this problem?
Thanks in advance!

[younes-zeboudj]

I have the same use case, I had to create a file 'functionX' , pass 'function1' to the 'func' attribute, make the obfuscator skip function1, obfuscate the file 'functionX', and insert a function with name 'function1' and the resulte of 'functionX' obfuscation as body to the obfuscated background.js

[younes-zeboudj]

workaround:

// javascript-obfuscator:disable
function myfunc=(param) => {
    console.log(param) // Hello World!
}
// javascript-obfuscator:enable

   const example = "Hello World!"
    chrome.scripting.executeScript({
        func: myfunc,
        args: [example],
        target: { tabId: tabId }
    })