steal-tools/doc/types/system-config.md

Futuristic build tools for ES6 Module applications.

@typedef {{}} steal-tools.SystemConfig SystemConfig
@parent steal-tools.types

Configuration values needed for StealJS to load modules. Some set of the following
values are required:

@option {String|Array<moduleName>} main The module, or modules, that should be 
imported.  This sets [System.main].  

@option {String} [config] The path to a configuration file. This
will also specify `baseURL`, and sometimes `main`. This sets [System.configPath].

@option {String} [baseURL] If a configuration file is not used, 
the [System.baseURL baseURL] value must be set.

@body

## Use

[steal-tools.build], [steal-tools.export], and [steal-tools.transformImport] all
take a `SystemConfig`, which configures the modules to load.

```
stealTools.build(SystemConfig, ...)
stealTools.pluginifier(SystemConfig, ...)
stealTools["export"]({system: SystemConfig, outputs: {...}});
```

If your `config` file specifies `main`, all that is needed is the `config` location:

```
stealTools.build({config: __dirname+"/package.json!npm"}, ...)
stealTools.pluginifier({config: __dirname+"/package.json!npm"}, ...)
stealTools.export({
  system: {config: __dirname+"/package.json!npm"}, 
  outputs: {...}
});
```

Otherwise, `main` and `config` are probably needed:


```
stealTools.build({
  config: __dirname+"/config.js",
  main: "myproject"
}, ...);

stealTools.pluginifier({
  config: __dirname+"/config.js",
  main: "myproject"
}, ...);

stealTools.export({
  system: {
    config: __dirname+"/config.js",
    main: "myproject"
  }, 
  outputs: {...}
});
```

If there is no `config`, you should specify the baseURL, so StealJS knows where to find your modules.