Nimble Prime Musketeers


    0.1.0 • Public • Published

    A tool to pack Node.js module files and module system emulator within one source file. That source file is executable on Google Apps Script environment( or perhaps other Javascript engines).


    • get more option values from package.json:_codegs object.
    • assume to be package.json when MAINFILE type is .json.

    Related package

    • 'codegs-core' includes some code core modules for GAS, and some Node.js core modules.

    First example

    I think looking this simple example is the easiest way to understand what happens by this tool.


    var lib = require('./lib.js');
    console.log('3 + 4 = ' + lib.sum(3, 4));


    module.exports.sum = function (a, b) {
        return a + b;

    those are valid Node.js modules.

    $ node main.js

    Then, try:

    $ code main.js

    and you see merged source code:

    $ code main.js
    function(exports, require, module, \__filename, \__dirname) {
    module.exports.sum = function (a, b) {
        return a + b;
    var lib = require('./lib');
    console.log('3 + 4 = ' + lib.sum(3, 4));
    function require(path) {
        require = (function () {

    That includes main.js lib.js, and it's executable.

    $ code main.js > out.js
    $ node out.js

    And out.js is executable on GoogleAppsScript environment.

    1. Create new GoogleAppsScript project and import 'gas-console'.

    2. Paste out.js into file.

    3. On menu bar, select require as execute function.

    4. Run or Debug

    That's how works.


    I like Google apps script(Server side javascript with online IDE for google apps), but not only, and also Jasmine - TDD/BDD. I tried to run jasmine on GAS. It works, but it's too far from TDD.

    After that I want to develop GAS software on my local pc, and I want local IDE/tools to support development.

    I need IDE/tools to:

    • Assist TDD/BDD(Jasmine etc.)
    • Support some module system.(ex. autocomplete methods/properties in other module)

    For this, instead of preparing special rich IDE/tools for GAS, I decided to write one small tool to make Node.js module files be executable on GAS.

    Full Compatibility with Node.js is not my goal. Actually, pure codegs provides minimum compatibility with Node.js module system. for more details, see Limitation.



    $ npm install -g codegs


    $ code mainfile [ options ] needs some information to work. Options let know that information.

    Minimum info to work

    • Main module
    • Project directory
    • Source files
    • Output file

    Main module

    Specify by command line, or package.json.

    • Javascript VM load and run this file first. and against GAS specification, this module will be put in global scope. It should be relative to the root of project directory.

    GAS entry functions should be defined in global scope with function statement.
    function onOpen() {}, function doGet() {}, or function YOURENTRYFUNCTION() {}, etc., has to be in this mainfile.

    Project directory

    Current working directory, or directory of package.json specified by command line.

    • needs file path information to pack files for require() function. But full path name(may include personal name) is not suitable to publish on GAS.For this, handle Project directory as a root(/).

    Source files or directory

    Command line option -s/--source or project directory.
    Or package.json specified with files tag.

    • One or more files/directories are able to set. Those files should be under the project directory.
    • If not set by commandline option, use project directory as source directory.

    Output file

    Command line option -o / --output or stdout.

    • Not set, outputs to standard output.

    Advanced Info to do more

    • node_modules
    • Core modules
    • Node core modules
    • Kernel file


    No command line option. All modules in PROJECT/node_modules/ will be packed.
    Or, only specified modules in package.json specified with dependencies tag.

    • can handle node_modules.

    • To load modules in /node_modules, no need to code fully filepath. Both of bellow are valid.

      var argv = require('/node_modules/argv.js');
      var argv = require('argv');

    Core modules

    PROJECT/core is default directory. or Any other directory set by option -c / --core.

    • Core modules are able to load without directory name such as 'assert', 'http' in Node.js. It's same as node_modules, but always this takes priority.

    • Modules in this directory, will assume to be core module. These modules will be laid out hidden path in output file.

    NodeCore modules

    PROJECT/node_core is default directory. or Any other directory set by option -n / --nodecore.

    • As same as Core modules. It's priority is between core module and node_modules.

      Core module > NodeCore modules > node_modules

    • This directory is for Node.js core modules. If you want to use Node.js core files such as util, assert, etc. put it in this directory.

    See also codegs-core.

    Kernel file

    Default file is 'module.js' in this package. Option -k / --kernel set it any other file.

    • Default kernel(module.js) is minimum & simple module emulator. But using additional modules, It's possible to extend kernel functions like global object process, console, timer functions,.. if you write.

    • can pack those additional modules with simple default kernel. and, use that package as a new kernel.

      ... This needs more explanation. I'll add later.

    Limitation and Enhancement

    No Node.js Global Objects.

    Node.js has some global objects(

    But pure provides only one function 'require'. No other global namespace pollution.

    See also codegs-core.

    Enhancemnet require to get Global Objects.

    Google Apps Script also provides global objects such as Logger, SpreadsheetApp, etc.

    'require()' of returns global object by name. It means this code returns original Logger object.

    var log = require('Logger');

    This is for debugging GAS code on Node.js. Using this, It's easy to inject API objects.

    When you want to use mock-Logger or mock-spreadsheet,.. write mock and put it in node_modules directory of parent directry.

    ex. if your project root dir is /home/path/to/project/, then put mock in /home/path/to/node_module.

    Node.js search that path and find mock. doesn't pack that mock(Because it locate outside project.). and require returns REAL objects.


    npm i codegs

    DownloadsWeekly Downloads






    Last publish


    • tyskdm