ecoco v0.2.3-3-beta

Ecoco (Extended COco COmpiler) v0.2.3-beta

It is assumed that you are familiar with coco language!

ecoco extends coco compiling features.

CLI

ecoco 0.2.3-3-beta

Usage:
	ecoco [options] file [arguments]
	ecoco file -c [options]

	i.e. if you want to execute (not compile)
	     then put arguments after file.

Options:

  --examples                 Show code examples

  --defaults                 Show default command line values

  --help, --usage, -h        Show help

  --version                  Show version

  --compile, -c              Equivalent to `coco -c`

  --bare, -b                 Equivalent to `coco -b`

  --uglify, -u, --compress   Compress output (uses `uglify-js`)

  --binary                   Output filename without `.js` and adds
                             `#!/usr/bin/env node` at the beginning of output
                             file.

  --include FILE             If FILE has `co` extension then AT COMPILE TIME
                             prepend FILE to source file. Otherwise if FILE has
                             `js` extension then AFTER compiling prepend FILE
                             to compiled file.

  --make-readme FILE         Replace `{CLI}` in `README.md.src` with `file
                             --usage` and save it to `README.md`.

  --no-colors                Disable color output

  --no-beep                  Disable error beep



Examples:

  ecoco -cbu awesome.co    compiles to awesome.js with `bare` and `uglify`
  ecoco --make-readme      compiles README.md.src into README.md
  ecoco binary.co --what   executes binary.co with `--what` argument

	

Headers

Adding these at the beggining of your source file will change Ecoco behaviour accordingly:

• #!b or #!bare like ecoco -b
• #!u or #!ugly or #!uglify like ecoco -u
• #!binary like ecoco --binary

• #!include=filename or #!include=filename.co like ecoco --include

Ecoco.json

Ecoco.json has similar functionality as Apaches' .htaccess. You put this file in the same folder as your .co script or in one of the parent folders (up to file system root). At the moment in Ecoco.json you can define two options: headers (array), and project_info (string).

Example:

{
	"headers":
	[
		"replace /^([\t]*)log (.*)$/gm, \"$1log $2, module.filename\"",
		"bare",
		"foo"
	],
	"project_info": "project info"
}

Following lines will be added to script just before compilation:

#!replace /^([\t]*)log (.*)$/gm, "$1log $2, module.filename"
#!bare
#!foo

And project info will be added in the .js file in top comment section.

Examples

fn = -> "ok!"

compiles to

(function(){
  var fn;
  fn = function(){
    return "ok!";
  };
}).call(this);

--

#!b

fn = -> "bare!"

compiles to

var fn;
fn = function(){
  return "bare!";
};

--

#!u

fn = -> "uglify!"

compiles to

(function(){var e;e=function(){return"uglify!"}}).call(this)

--

node_bin.co:

#!bin
process.stdout.write "I'm alive!\n"

compiles to node_bin:

#!/usr/bin/env node
(function(){
  process.stdout.write("I'm alive!\n");
}).call(this);

--

example.co:

#!include=include_me.co
im_not_alone = true

include_me.co:

you_are_not_alone = true

ecoco example.co compiles to:

(function(){
  var you_are_not_alone, im_not_alone;
  you_are_not_alone = true;
  im_not_alone = true;
}).call(this);

Install

npm install -g ecoco

or

git clone https://github.com/jan-swiecki/ecoco && cd ecoco && npm install && npm link

or if you want to build

git clone https://github.com/jan-swiecki/ecoco && cd ecoco && npm install && coco index.co index.co && npm link

Changelog

• 0.2.3-beta

  Added ecoco.json support.