violentmonkey: [BUG] `GM.xmlHttpRequest()` returns non-200 response

I didn’t value my life for a long time so I didn’t know when to stop and got myself in situations where I nearly died several times.

You’re looking at the awaited result i.e. await GM.xmlHttpRequest().

To see the returned result of the function you should look at GM.xmlHttpRequest(). You’ll see that in the specification it’s undefined, in Violentmonkey it’s a control object with abort inside, in Tampermonkey it’s Promise with abort inside.

You can’t use await anywhere except Tampermonkey if you want your script to be compatible with other specification-compliant managers.

You can use the same approach you’ve already used in your updateCheck().

You can also combine it with the standard promisification technique:

const res = await new Promise((resolve, reject) => GM.xmlHttpRequest({onload: resolve, onerror:reject}))

so it would be wise to avoid this mindset and instead try to catch up with how they implement things

Tampermonkey’s approach is not always wise.

if you also want to become a standard one day

But we don’t.