Discussies » Greasy Fork-feedback
await is valid without async function now, but greasyfork shows error when I update my script.
Can you provide example code?
Can you provide example code?
The error shown when I try to update one of my script.
the below code in the link is the whole lines of my script that I'm trying to update.
the script that I'm trying to post on greasyfork
Greasy Fork uses mini_racer, which depends on libv8-node, to parse scripts. We're using the latest of both, so not much can be done until they release new versions.
Thanks for letting me know Jason ! :)
Is there any follow-up on this issue? I have the same problem.
Modern browsers have supported top-level await for some time now (almost two years). The bug does not occur on TamperMonkey. But libv8-node
doesn't seem to follow this feature efficiently.
Here is a simple reference for you to learn the concept of async/await.
https://greasyfork.org/en/discussions/development/187288-converting-gm-setvalue-gm-getvalue-to-gm-setvalue-gm-getvalue
Is there any follow-up on this issue? I have the same problem.
Modern browsers have supported top-level await for some time now (almost two years). The bug does not occur on TamperMonkey. Butlibv8-node
doesn't seem to follow this feature efficiently.
why not just
(async ()=>{
// your code here
})();
libv8-node has been updated since my last post, so I've deployed an upgrade just now. Not sure if that fixes anyone's issue as no sample code has been provided (the link for sample code above is dead now).
libv8-node has been updated since my last post, so I've deployed an upgrade just now. Not sure if that fixes anyone's issue as no sample code has been provided (the link for sample code above is dead now).
I've tried removing top-level IIFE from my scripts.
But unfortunately, libv8-node
still doesn't seem to support top-level await
, and still get "Code contains errors: Uncaught SyntaxError: await is only valid in async functions and the top level bodies of modules at undefined:20:22".
Thanks for the reply, I'll keep an eye on libv8-node :)
https://greasyfork.org/en/scripts/26731-twitter-image-new-tab-redirect-original?locale_override=1
Is it maybe because Tampermonkey is running the script as a module?
Is it maybe because Tampermonkey is running the script as a module?
I think so. top-level await has been turned on by default as an experimental feature of Tampermonkey for a while now.
How long would that take to be fixed ?