commit | 66e048c29b8f006c8a1f0a3f74d30c72da1d6d1c | [log] [tgz] |
---|---|---|
author | Benjamin Prosnitz <bprosnitz@google.com> | Wed Feb 10 07:41:10 2016 -0800 |
committer | Benjamin Prosnitz <bprosnitz@google.com> | Wed Feb 10 07:41:10 2016 -0800 |
tree | 5d392d50f22e85e18cff828f85ae734a8472b1c2 | |
parent | 515e21c72947ca3dc42fa9ed7aa146c748615227 [diff] |
js: Generate vdl.RawBytes by default for any MultiPart: 3/4 Change-Id: I2d71fe2b33a94fd560ee0fbc143a2ff7e1c1edfb
This repository defines the JavaScript API for Vanadium. The client and server APIs defined here work both in Node.js and the browser.
npm install --save vanadium/js
The entry point to the API is through a module called vanadium
, everything else is considered private and should not be accessed by the users of the API.
The vanadium
module is exported as a global in the browser JavaScript library and for Browserify and Node.js the “main” property in the package.json
points to /src/vanadium
making it the index module and therefore Browserify and Node.js users can gain access to the API with:
var vanadium = require("vanadium");
One of the goals of this project is to only write the code once and have it run in both Node.js and browsers. Therefore, specific build and testing steps have been designed in the project to ensure this goal.
When run in a browser, vanadium.js
expects that the vanadium extension will be installed.
Bugs and feature requests should be filed in the Vanadium issue tracker.
GNU Make is used to build and test Vanadium.
Build everything:
make build
Test everything:
make test
Run a specific test suite:
make test-unit make test-unit-node make test-unit-browser make test-integration make test-integration-node make test-integration-browser
Remove all build and testing artifacts:
make clean