4 ms·

Eh, it's very outdated. For example, "YouTube Plus" was sold by the author years ago (to shady party no less) and "Iridium" is his new endeavor on Y2B enhanceme

Eh, it's very outdated. For example, "YouTube Plus" was sold by the author years ago (to shady party no less) and "Iridium" is his new endeavor on Y2B enhancement, which was also abandoned. To be honest, I don't think there is any point to include specific scripts to begin with. https://greasyfork.org/ https://greasyfork.org/ probably is a better place to find them. Just list all the "meta" sites (toolings, host sites, articles) about userscript is probably better and easier. On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth.

cookie_monsta 5y ago
> On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth. Agreed. Even stranger is that some errors end up in the console but others do not. Syntax errors particularly seem to fail silently. If I'm putting together something that I know will be more than a dozen lines or so (or is targeting a page sitting behind logins and extra navigation) I will just save the target page as a local file and write the JS into that file and debug as normal until it's working, then copy the JS over to a userscript.
- jtvjan 5y ago
  At least for Firefox, you can look at the browser error console (Ctrl+Shift+J) to always see error messages, even if the script failed to inject.
  - cookie_monsta 5y ago
    Not for me. This: // ==UserScript== // @name HN test // @version 1 // @grant none // @include https://news.ycombinator.com/\\ https://news.ycombinator.com/\\* // ==/UserScript== alert("hello" shows nothing in a userscript, but: Uncaught SyntaxError: missing ) after argument list test.htm:23 in a local page
gizdan 5y ago
I don't know about syntax errors (I've seen them fail silently), however, at least with ViolentMonkey and Firefox, you can use an external editor for development and for debugging you can step through using the debugger.
insin 5y ago
> On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth. Develop it as an extension with the script as your content_script, and use web-ext [1] to run it. You can then develop in your regular editor, use your browser's extension debugging tools, and web-ext will automatically reload it when you change stuff. Most of my extensions use a .user.js file as their content_script, which I can also publish directly to Greasy Fork. [1] https://github.com/mozilla/web-ext#web-ext https://github.com/mozilla/web-ext#web-ext
Ginden 5y ago
I'm building with Rollup and TS. See eg. this config. https://github.com/Ginden/userscripts/tree/master/hacker-news-improvements https://github.com/Ginden/userscripts/tree/master/hacker-new... Then I do `npm run build && cat dist/index.ts | xclip` and replace code.
asddubs 5y ago
Seems like that's a theme for these "awesome-*" lists. Outdated and Questionable links mixed with good ones

cookie_monsta 5y ago

> On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth. Agreed. Even stranger is that some errors end up in the console but others do not. Syntax errors particularly seem to fail silently. If I'm putting together something that I know will be more than a dozen lines or so (or is targeting a page sitting behind logins and extra navigation) I will just save the target page as a local file and write the JS into that file and debug as normal until it's working, then copy the JS over to a userscript.

jtvjan 5y ago
At least for Firefox, you can look at the browser error console (Ctrl+Shift+J) to always see error messages, even if the script failed to inject.
- cookie_monsta 5y ago
  Not for me. This: // ==UserScript== // @name HN test // @version 1 // @grant none // @include https://news.ycombinator.com/\\ https://news.ycombinator.com/\\* // ==/UserScript== alert("hello" shows nothing in a userscript, but: Uncaught SyntaxError: missing ) after argument list test.htm:23 in a local page

gizdan 5y ago

I don't know about syntax errors (I've seen them fail silently), however, at least with ViolentMonkey and Firefox, you can use an external editor for development and for debugging you can step through using the debugger.

insin 5y ago

> On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth. Develop it as an extension with the script as your content_script, and use web-ext [1] to run it. You can then develop in your regular editor, use your browser's extension debugging tools, and web-ext will automatically reload it when you change stuff. Most of my extensions use a .user.js file as their content_script, which I can also publish directly to Greasy Fork. [1] https://github.com/mozilla/web-ext#web-ext https://github.com/mozilla/web-ext#web-ext

Ginden 5y ago

I'm building with Rollup and TS. See eg. this config. https://github.com/Ginden/userscripts/tree/master/hacker-news-improvements https://github.com/Ginden/userscripts/tree/master/hacker-new... Then I do `npm run build && cat dist/index.ts | xclip` and replace code.

asddubs 5y ago

Seems like that's a theme for these "awesome-*" lists. Outdated and Questionable links mixed with good ones