| commit | 97eb0bdda5a9ecc996b005d4ccc58c9e84526a8e | [log] [tgz] |
|---|---|---|
| author | Nicolas Lacasse <nlacasse@google.com> | Wed Mar 23 15:56:33 2016 -0700 |
| committer | Nicolas Lacasse <nlacasse@google.com> | Wed Mar 23 16:28:21 2016 -0700 |
| tree | 457b99ad837b01b65c193d6eecae74310e15035d | |
| parent | 277f82fa43db08cbfd04fa93e290a6dd4d99e2d3 [diff] |
Update vanadium.js to node 4.4.1 Also: * Update all package.json dependencies to latest version. * Remove browserify. * Remove extension. * Remove integration tests. The unit, vdl, and vom tests remain and are passing. MultiPart: 1/5 Change-Id: I957311b32c6efa95be36e306ac6afc69df6ad215
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