<commit_before># Vanadium JavaScript

This repository defines the JavaScript API for Vanadium.
The client and server APIs defined here work both in [Node.js] and the browser.

## Install

## Install
Since Vanadium is currently hosted in private repositories, you would need to
[setup SSH keys for Github]
(https://help.github.com/articles/generating-ssh-keys/)
first and then use npm to install directly from GitHub:

    npm install --save git+ssh://git@github.com:vanadium/js.git

## Usage

Documentation for this API is available at https://jsdoc.v.io/

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<commit_msg>js: Removing some pre-public specific stuff.<commit_after># Vanadium JavaScript

This repository defines the JavaScript API for Vanadium.
The client and server APIs defined here work both in [Node.js] and the browser.

## Install

    npm install --save vanadium/js

## Usage

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
{'fraction_non_alphanumeric': 0.06607310215557638, 'fraction_numerical': 0.0, 'mean_word_length': 4.310945273631841, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 1, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3448520', 'n_tokens_mistral': 587, 'n_tokens_neox': 547, 'n_words': 313}