javascript-refactoring

JavaScript modularization solves the problem of duplicated logic across gh-aw workflows by extracting shared code into reusable .cjs files. You create modules under pkg/workflow/js, export functions, and import them in multiple workflow scripts to eliminate duplication and simplify maintenance.

To bundle local CommonJS dependencies for gh-aw workflows, you must wire new .cjs modules into GetJavaScriptSources(). The bundler then inlines these local dependencies during the build process, ensuring workflow scripts have all required logic available at execution time.

Bundled JavaScript executes immediately instead of exporting main when top-level scripts invoke functions at runtime. To fix this, refactor scripts to export main without immediate invocation so the gh-aw bundler can properly inject execution logic during the build process.

Yes, you can use .cjs modules to simplify testing for shared JavaScript utilities. Extracting logic into separate CommonJS modules under pkg/workflow/js allows you to add targeted unit tests for each utility, ensuring reusable functions are validated independently before workflow integration.

The best way to refactor a monolithic JavaScript script for multiple workflows is to extract shared logic into a standalone .cjs module, register it in GetJavaScriptSources(), and import it where needed. This modularization approach enables reuse and aligns with gh-aw's bundling process.