History

joeduffy b4b4d26844 Add pkg/util/rpcutil to cut down on some plugin boilerplate This change eliminates some of the boilerplate required to create a new plugin; mostly this is gRPC-related code.		2017-03-11 09:23:09 -08:00
..
aws	Add pkg/util/rpcutil to cut down on some plugin boilerplate	2017-03-11 09:23:09 -08:00
cocojs	Fix install scripts to use `coco pack verify`	2017-03-10 09:37:16 -08:00
coconut	Fix install scripts to use `coco pack verify`	2017-03-10 09:37:16 -08:00
coconutx	Coconut!	2017-02-25 07:25:33 -08:00
README.md	Simplify the library README	2017-03-11 09:01:33 -08:00

README.md

coconut/lib

This directory contains some libraries that Coconut programs may depend upon.

Overview

The Coconut standard library underneath coconut/ is special in that every program will ultimately use it directly or indirectly to create resources.

Similarly, cocojs/ is the CocoJS compiler's runtime library, and so most CocoJS programs will on it.

Note that these are written in the Coconut subsets of the languages and therefore cannot perform I/O, etc.

Installation and Usage

Eventually these packages will be published like any other NPM package. For now, they are consumed only in a development capacity, and so there are some manual steps required to prepare a developer workspace.

For each library <lib> you wish to use, please see its install.sh script in its root directory. This performs installation so that it can be used simply by adding a dependency to it.

We currently use NPM/Yarn symlinks to ease the developer workspace flow. As such, you will need to run:

yarn link <lib>

In a project that intends to consume <lib> before actually using it. For example, yarn link @coconut/coconut.