It sorta depends whether you expect users to use your construction files, whether you expect them to be building their own, and how often you expect to be editing it all after release.
For example, with
WorldPorter (a script for OPs, which copy/pastes structures directly using Minecraft server commands), I provide the main code via a single pastebin download, and separate to that, a number of demo structures combined together using
Package. There are a number of other scripts around for handling distribution of multiple files, eg
Packman,
Grin-Get…
If you always want to distribute all your files together, you might put each into a separate paste, and have the main script file download all the others the first time you run it:
if not fs.exists("addonScript1") then shell.run("pastebin get <pasteID> addonScript1") end
if not fs.exists("addonScript2") then shell.run("pastebin get <pasteID> addonScript2") end
etc...
This way, you don't have to rebuild a combined archive every time you want to edit one of the extra script files. It's generally how I distribute any projects which
need to have certain extra files.