How do I make a script both executable on its own an serve as a library for other scripts?

Hi @orib7317974 , Also this resource might help:

https://extendscript.docsforadobe.dev/

The section on includes:

https://extendscript.docsforadobe.dev/extendscript-tools-features/preprocessor-directives.html

.jsxinc is suggested for the include file, but as others have noted .jsx also works.

Any functions, variables, or constants you write in the include file are effectively public—you can call them from the script that includes the code. So this file has an exposed function—gerWorldString(), constant—MAGIC_NUMBER, and variable—vNum:

/**
* External function example saved with .jsxinc in the same directory as script 
* @ param s string
* @ return string + parameter 
*/

function getWorldString(s){
  return "From Hello World: " + s
}

/**
* A read only constant
*/
const MAGIC_NUMBER = 1.045

/**
* A read write variable
*/
var vNum = 5

I named the file HelloWorld.jsxinc and included it with a script in the same directory. From that script I can call the public functions, constants, and variables:

#include "HelloWorld.jsxinc"


$.writeln(getWorldString("Hi There!"))
//From Hello World: Hi There!

$.writeln(MAGIC_NUMBER)
//retuns 1.045

$.writeln(vNum)
//returns 5

vNum = 10;
$.writeln(vNum);
//returns 10

Another note on the syntax Mark used with the include command:

If you search the forum you'll find most of the (older) code snippets using include with this syntax:

#include

Why, because most of the old code was written with and tested with the ESTK (ExtendScript Toolkit App) and also, at least I think so, because //@include was not documented for a long time.

Both versions of the syntax will work when you run the script from the Scripts > User panel or with the old ExtendScript Toolkit App ( still installable and usable on Windows 10 or 11 ) . However, when running the script with the Adobe ExtendScript debugger from VSCode you have to use this syntax:

//@include

In this case the // does not state the beginning of a comment. The directive @include behind the // is executed.

So be careful when writing comments. Or use this for commenting your code:

/*

//@include is a powerful way to access code from a different script file sharing the same script language.

*/

Regards,
Uwe Laubender
( Adobe Community Expert )

Hi @orib7317974 ,

note, that you can also use app.doScript().

That would be especially useful if you are in a situation where you like to use a mix of scripting languages.

Example: when on macOS you could include the executable code of an AppleScript file in your ExtendScript code.

See into ExtendScript DOM documentation compiled by Gregor Fellenz:

https://www.indesignjs.de/extendscriptAPI/indesign-latest/#Application.html#d1e42253__d1e45802

app.doScript( yourAppleScriptFile , ScriptLanguage.APPLESCRIPT_LANGUAGE );

With the current version of InDesign 2023 including a UXP Script should also be possible with app.doScript(). Did not test it yet:

app.doScript( yourUXPScriptFile , ScriptLanguage.UXPSCRIPT );

Or you have no script file at all, but the code of an AppleScript or an UXP Script at hand and provide it as string for the first argument of the doScript() method. Search the forum, there are many examples with AppleScript running from a doScript() method...

Regards,
Uwe Laubender
( Adobe Community Expert )

Oh, I think I found the answer: