I figured it out (tested in sandbox), thank you for all the help

My understanding was that assets are presentation artifacts, I missed the "custom scripts" mentioned in the one sentence. Thank you for your help, this should allow for some leniency. My initial feeling was that "{#asset some-asset.js}" would work within the script.

Thank you for verifying what I thought. Unfortunately, I will just have to replicate logic across each custom script. Not a problem now, but being able to modularize repeated functionality could be useful across many reports.

Is there a preferred way (JSReport way) to create a script that is reusable within report specific scripts? I had locally created a set of methods that did all of my HTTP callings and used them in specific scripts for specific reports. This allowed me to not have to repeat the ceremony of working with a module like HTTP in each report that I create. I achieved this by inspecting the filesystem and requiring through the path to the content file. Currently, as I can tell, jsreportonline does not have allowedModules: "*", so I think I am stuck.

Am I looking to do more than what is currently (or ever) capable? Or is there a way that I have not understood through the documentation?

Scripts

1. API-Access = abstraction over HTTP/Request/whatever
2. Invoice Script -> require(API-Access)
3. Summary Script -> require(API-Access)

Reports

1. Invoice -> references "Invoice Script"
2. Summary -> references "Summary Script"

Thank you in advance