Discussions » Greasy Fork Feedback
"Code uses invalid external script" warning for @require from update.greasyfork.org — how to fix?
Probably the issue is that spaces are not valid in URLs. Use the URL provided at https://greasyfork.org/en/scripts/565619-jut-su-auto-core-library, where spaces are escaped.
https://update.greasyfork.org/scripts/565619/Jutsu%20Auto+%20Core%20Library.user.js
fetch("https://update.greasyfork.org/scripts/565619/Jutsu%20Auto+%20Core%20Library.user.js")
404 error
but
https://update.greasyfork.org/scripts/565619/1751507/Jutsu%20Auto%2B%20Core%20Library.js is ok
According to RFC 3986, "+" is allowed in URL path. GreasyFork shall fix it.
When "+" is in query, it has to be encoded, but not in path.
see encodeURI("https://update.greasyfork.org/scripts/565619/Jutsu Auto+ Core Library.user.js")
Thx

Hello Greasy Fork moderators and community,
When trying to upload/update my userscript, I received the following warning from the editor:
Code uses invalid external script: @require https://update.greasyfork.org/scripts/565619/Jutsu Auto+ Core Library.user.js
This is my own helper library (Jutsu Auto+ Core Library), published as a separate script on Greasy Fork (ID 565619).
Questions:
Why is @require from https://update.greasyfork.org/... considered invalid or not allowed?
Is it prohibited to @require another script hosted on Greasy Fork itself?
What is the correct way to include my own library code in 2026?
Should I inline the entire library directly into the main script (if it's small)?
Host the library externally (e.g. GitHub raw, jsDelivr) and use @require there?
Publish the library as a "library" type script on Greasy Fork and @require it differently?
Are there any official guidelines or moderator recommendations about using @require for shared code/libraries?
I want to follow all rules and make sure my script passes moderation without issues.
Script links for reference:
Main script: [link to your main script]
Library script: https://greasyfork.org/en/scripts/565619-jutsu-auto-core-library
Thank you very much for your help and clarification!
Best regards,
Rodion