Strict Mode wrapper prevents `@require` libs from working

[LeoNatan]

Hello,

Some change, be it an OS update or a Userscripts update, has broken one of my scripts, on macOS and iOS. I have been on iOS 16 betas for a while, and I think the script worked in that period, and only recently stopped working, so I suspect it’s a change in Userscripts.

The exception thrown:

TypeError: 'arguments', 'callee', and 'caller' cannot be accessed in this context.

The script:
https://raw.githubusercontent.com/LeoNatan/NFOHump/master/EmbedVideos/NFOHumpEmbedVideos.user.js

Can be tested on:
https://www.nfohump.com/forum/viewtopic.php?t=114985

System Information:

macOS or iOS version: 13.1 Beta, 16.2 Beta
Userscripts version: 4.3.1 (62)
Safari version: Version 16.1 (18614.3.2.11.2)
Is this issue related to script injection? Yes
Did the test script (pasted above) successfully run on your machine? Yes

[quoid]

This error seems to be caused by one of your @require resources, I think the reddit one. All code, including @require resources are wrapped in an anonymous function using strict mode which seems to be the cause of the issue. I've confirmed that disabling strict mode enables your userscript to function as expected (ie. gifs load in that forum post).

The dilemma here is that when using a @require library, the userscript author has little/no control over how it is programmed. This means they can not update the code to abide by strict mode guidelines.

I am going to update the title of this issue to better reflect the issue.

[LeoNatan]

Is this a new change? Until recently, this script used to work as expected.

[quoid]

Yes it changed the last update. I'm hoping we can push a hotfix for this in short order, later today if poss.

[LeoNatan]

Also worth mentioning that the script functions as expected under Tampermonkey on Firefox.

Perhaps an option can be given somehow, allowing script developers to opt-in to strict mode? Or opt-out.

[quoid]

That's where I am leaning. Users can opt-in if they so choose.

[LeoNatan]

Perfect, thank you for your quick response!