You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is only one object provided to user scripts now, named GM.
It has several properties. One of them is info – the equivalent of the old GM_info.
There are also several methods of this object:
getResourceUrl,
deleteValue,
getValue,
listValues,
setValue,
xmlHttpRequest.
To use these methods you still need @grant, and use the new name, e.g.:
// @grant GM.setValue
The new form has a dot, where the old form has an underscore.
You may specify both @grants, if you'd like to be compatible with Greasemonkey 4 and other user script engines at the same time.
As of today, there is no support for:
In other words, the 'Greasemonkey' environment should be updated to include the GM object and its properties. (all the old GM_* grants should also be maintained, even the 4 currently not supported ones, for use by other script engines) .
Continuation from eslint/eslint#9621 (comment) :
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using? default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
What did you expect to happen?
No errors should be found.
What actually happened? Please include the actual, raw output from ESLint.
It found the following 2 errors:
That's because, since Greasemonkey 4.0 :
The complete list of the
GM
obect's properties is the following: (Greasemonkey_Manual:API)GM.info
GM.deleteValue
GM.getValue
GM.listValues
GM.setValue
GM.getResourceUrl
GM.openInTab
GM.setClipboard
GM.xmlHttpRequest
, andunsafeWindow
In other words, the 'Greasemonkey' environment should be updated to include the
GM
object and its properties. (all the oldGM_*
grants should also be maintained, even the 4 currently not supported ones, for use by other script engines) .I also quote the reply by @platinumazure :
The text was updated successfully, but these errors were encountered: