#GREASY FORK CODE#

The cookie is used to store the user consent for the cookies in the category 'Performance'. This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category 'Other. The cookies is used to store the user consent for the cookies in the category 'Necessary'. Find related and similar companies as well as employees by title and. This cookie is set by GDPR Cookie Consent plugin. View Greasy Fork (location, revenue, industry and description. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category 'Functional'. The cookie is used to store the user consent for the cookies in the category 'Analytics'. These cookies ensure basic functionalities and security features of the website, anonymously. It's much simpler to do than writing a standalone browser extension.Necessary cookies are absolutely essential for the website to function properly. The key takeaway is that it isn't difficult to write a user script if you have some basic knowledge of writing JavaScript for the browser. Still, the general approach will be useful in other scenarios as well.

#GREASY FORK CODE#

Of course, the code is very specific to the problem I was solving. You can check the script I've written in my GitHub repository. To automate updates, you can even set up a web hook. If you host your script on GitHub (or another Git host), the process is even simpler as you can import it from there. Publishing a script on GreasyFork is just a matter of filling out a simple form. Despite that, for me the benefits of using Visual Studio Code overweigh the inconvenience of having to copy the script to test it. I found a Stackoverflow answer with instructions for loading the script in Tampermonkey directly from the file system but I couldn't get it to work. Instead of simply saving it, I have to copy and paste it to the Tampermonkey editor and save it there. And it even helped me notice a couple of mistakes in my code without running it.Īdmittedly, this approach adds some overhead to testing the script. Even without TypeScript types, it can provide great code completion and help for methods used. You can open it in the built-in editor from there to modify it at a later time:Īlthough the editor is decent, I prefer Visual Studio Code for writing JavaScript. When you save the script for the first time, it appears in its Installed userscripts list. You can open it via the Add a new script. I handle events using the addEventListener method: const copyAnchor = document.createElement( 'a') ĬtAttribute( 'title', iconLabel) ĬopyAnchor.addEventListener( 'click', copyToClipboard) įilterDropdownTitleElement.appendChild(copyAnchor) Ī basic development environment is provided by the Tampermonkey extension. I used unobtrusive JavaScript principles to add interaction to the page, i.e. In my case, most of the code was inspecting the DOM using the querySelector and querySelectorAll methods: const filterDropdownTitleElement = document.querySelector( Learn about running Greasy Fork locally and contributing code. Contributing Greasy Fork welcomes contributions. Help Post in the Greasy Forum for help with Greasy Fork, user scripts, user script managers, or related. Damir Arh // MIT // // */achievements* // none // =/UserScript= Greasy Fork is an online repository of user scripts and user styles. The most important part is the script header with meta keys describing the script and specifying when it's going to be activated: // =UserScript= // Copy TrueGaming achievement list // // 1.0.0 // Copies the achievements/trophies from the True Achievements. But since user scripts are mostly just additional JavaScript running in the context of the web page, there isn't much to learn that's specific to user scripts. The community-maintained documentation is rather brief and not updated too often. Only recently has a missing feature on a web page bothered me enough to consider creating a user script myself. I've been using a couple of GreasyFork scripts with Tampermonkey Firefox extension for a while.

Greasy fork