Notice: Development on this repository is currently on pause during our v3 rearchitecture. Please see storj/storj for ongoing v3 development.
The official Storj library, for node.js and the browser.
This library is currently in early beta. It is released for testing purposes only. Files uploaded via storj.js are not currently compatible with the reference implementation. If you are developing an application, we strongly recommend that you use libstorj via bindings.
If you are building an application that will run outside of a browser, such as a web server, you should use Node.js. From the root of your project directory, alongside your package.json, run:
npm install --save storj
Note: during the beta, this package will not be available via npm. Instead, install with the following syntax:
npm install --save https://github.com/storj/storj.js
Download the Storj.js library from our releases page and place it alongside the index.html file for your website, saving it as storj.js. Then, in index.html include:
<html>
<head>...</head>
<body>
...
<script src="./storj.js"></script>
...
</body>
</html>The files on our releases page are named after the version of the ECMAScript they target. If you are wanting to target older browsers, use storj.es5.js which targets ES5, othwise use storj.es6.js.
var Storj = require('storj');
var storj = new Storj()<script src="storj.js"></script>
<script>
var storj = new Storj(options);
...
</script>Storj.js exposes an isomorphic API that works both in the browser and in node.js!
Create a new Storj instance, which will be used to talk across the storj protocol. This object will emit the ready event when it has finished being configured.
The optional opts allows you to override the default behaviour of this object. The opts object is how you will pass in your user credentials if you need to work with private buckets.
opts:
{
bridge: STRING, // The url of the bridge to talk to, defaults to https://api.storj.io
basicAuth: OBJECT, // Used for any requests that require authentication, this is your username and password
key: STRING, // Private key, used for any requests that require authentication
encryptionKey: STRING // Used to encrypt and decrypt data stored in private buckets
}
basicAuth should be of the form:
{
email: STRING,
password: STRING
}
If you need to use authentication in your application, we strongly suggest you use the key method as it provides a higher level of security.
Both basicAuth and key are optional, but you may only provide one or the other. If you use basicAuth, the library will assume that you already have registered a public key with the bridge you are authenticating with. To create a public/private key pair for you and register it to your account you can use the generateKeyPair and registerKey API.
If you provide a key, this key will be used to authenticate every request moving forward.
Emitted when the library encounters a catastrophic error that will probably prevent normal operation moving forward. When an error is emitted, you should cleanup your Storj object and create a new one.
Emitted when the Storj object is ready to communicate with the storj network.
Create a new public/private KeyPair for authenticating against the Storj network. Note, this function will not register this key with your account, you must provide storj.registerKey with the returned public key to do that.
Register a public key with the Storj network. cb will be called with an Error if something goes wrong or null otherwise.
var keypair = storj.generateKeyPair();
storj.registerKey(keypair.getPublicKey(), function(e) {
if(e) { /* failed to register key */ }
});Get a list of all public keys stored for the current user. cb will be called with an Error if something goes wrong, or will be passed an array keys, where each element of the array is an object in the form:
{
user: String, // The user the key belongs to
key: Striong, // The public key itself
id: String // The unique id of the key
}Remove a public key from the Storj network. cb will be called with an Error if something goes wrong or null otherwise.
Create a new encryption key, which can be used to encrypt/decrypt files on the storj network. Certain operations, such as createFile, require that Storj was provided an encryption key when constructed. Keep track of this, as it will be necessary to retrieve your files in the future.
var key = storj.generateKeyPair().getPrivateKey();
var encryptionKey = storj.generateEncryptionKey();
var storj = new Storj({ key, encryptionKey });
// storj can now perform bucket operations and upload/download filesCreate's a bucket on the storj network with the requested name. cb will be invoked with an error if creating the bucket fails, otherwise meta will contain metadata for the bucket created.
meta has the following properties:
{
id: String, // The bucket id of the newly created bucket
name: String // the name of the newly created bucket
}Get the metadata for a bucket. cb will be invoked with an error if getting the meta-data fails, otherwise meta will have the following properties:
{
id: String, // The id of the bucket
name: String // The name of the bucket
}Get a list of all buckets associated with the currently authenticated account on the storj network. cb will be invoked with an error if getting the list of buckets fails, or with an array of meta-data about the buckets. Each element of the buckets array will have the following properties:
{
id: String, // the bucketID of the bucket
name: String // the name of the bucket
}Give public access to an existing bucket. cb will be passed an Error if something goes wrong, or undefined otherwise. perms should be an array of permission strings, currently supported permissions are:
PULL- Allow others to download from this bucketPUSH- Allow users to upload to this bucket
storj.makePublic(bucketId, ["PULL", "PUSH"], function(e) {
if(e) {
/* Handle Error */
}
/* Bucket is now public with both pull and push permissions */
})Remove a bucket from the Storj network. cb will be invoked with an error if the operation fails, or null otherwise.
Upload a file to a bucket.
bucketId - the id of the bucket that we will be uploading the file to (String)
fileName - the name of the file we are uploading, with it's extension (String)
file - the contents of the file and can be any of the following:
- a
stream.Readable - a
Stringwith the plain-text contents of the file - a
Blob
opts is optional, and allows you to specify some of the file's metadata:
{
fileSize: Number, // Size of the file in bytes, required if `file` is a stream
}cb is an optional function that will be registered as a listener on the returned File's done event.
bucketId - the id of the bucket the file lives in (String)
fileId - the id of the file itself (String)
cb - an optional function that will be registered as a listener for the done event on the returned file object
Get a list of files stored in a bucket on the Storj network. cb will be invoked with an Error first if the operation fails, or null otherwise. files will be an array of meta-data about the files, each element will have the following properties:
{
id: String, // the id of the file
name: String, // the name of the file
mimetype: String // the mime-type of the file
}Remove a file from the Storj network. cb will be invoked with an Error first if the operation fails, or null otherwise.
The name of the file.
The mimetype of the file.
The length of the file in bytes.
A number between 0 and 1 (inclusive) reflecting what percentage of the file has been downloaded from the network. To determine how many bytes have been downloaded, you can multiply file.length by file.progress.
Emitted when a File has finished either uploading or downloading it's contents.
Emitted when the File has finished being setup and is ready to begin transfering data. You can listen for this event if you are planning on tracking the progress of an upload/download.
Emitted when the File encounters an unrecoverable error either during setup or during upload/download. If this is emitted, it is safe to assume the File is in a corrupted state and the upload/download should be restarted from the beginning.
Emitted when data has been downloaded from the network, this can be used for tracking the value of file.progress. The callback will be provided the chunk of data that was pulled over the network.
Note: This event is not yet implemented. Registering the
dataevent will not throw an error, but the event will never be triggered. To track implementation progress, follow issue #72
Create a readable stream to the file. Pieces of the file will become available from the stream as soon as they are downloaded from the network.
Returns a Buffer representation of the file. If the file is downloading when getBuffer is called, the cb will be called with a Buffer as soon as the file finishes downloading.
Show the file in a the browser by appending it to the DOM. This is a powerful function that handles many file types like video (.mp4, .webm, .m4v, etc.), audio (.m4a, .mp3, .wav, etc.), images (.jpg, .gif, .png, etc.), and other file formats (.pdf, .md, .txt, etc.).
The file will be fetched from the network and streamed into the page (if it's video or audio). In some cases, video or audio files will not be streamable because they're not in a format that the browser can stream so the file will be fully downloaded before being played. For other non-streamable file types like images and PDFs, the file will be downloaded then displayed.
rootElem is a container element (CSS selector or reference to DOM node) that the content
will be shown in. A new DOM node will be created for the content and appended to
rootElem.
If provided, opts can contain the following options:
autoplay: Autoplay video/audio files (default:true)controls: Show video/audio player controls (default:true)maxBlobLength: Files above this size will skip the "blob" strategy and fail (default:200 * 1000 * 1000bytes)
If provided, callback will be called once the file is visible to the user.
callback is called with an Error (or null) and the new DOM node that is
displaying the content.
file.appendTo('#containerElement', function (err, elem) {
if (err) throw err // file failed to download or display in the DOM
console.log('New DOM node with the content', elem)
})Streaming support depends on support for MediaSource API in the browser. All
modern browsers have MediaSource support.
For video and audio, storj.js tries multiple methods of playing the file:
videostream-- best option, supports streaming with seeking, but only works with MP4-based files for now (usesMediaSourceAPI)mediasource-- supports more formats, supports streaming without seeking (usesMediaSourceAPI)- Blob URL -- supports the most formats of all (anything the
<video>tag supports from an http url), with seeking, but does not support streaming (entire file must be downloaded first)
The Blob URL strategy will not be attempted if the file is over
opts.maxBlobLength (200 MB by default) since it requires the entire file to be
downloaded before playback can start which gives the appearance of the <video>
tag being stalled. If you increase the size, be sure to indicate loading progress
to the user in the UI somehow.
For other media formats, like images, the file is just added to the DOM.
For text-based formats, like html files, pdfs, etc., the file is added to the DOM
via a sandboxed <iframe> tag.
Like file.appendTo but renders directly into given element (or CSS selector).
Get a W3C Blob object which contains the file data.
The file will be fetched from the network, and callback will be called once the file is ready. callback must be specified, and will be called with a an Error (or null) and the Blob object.
Get a url which can be used in the browser to refer to the file.
The file will be fetched from the network and callback will be called once the file is ready. callback must be specified, and will be called with a an Error (or null) and the Blob URL (String).
This method is useful for creating a file download link, like this:
file.getBlobURL(function (err, url) {
if (err) throw err
var a = document.createElement('a')
a.download = file.name
a.href = url
a.textContent = 'Download ' + file.name
document.body.appendChild(a)
})Get the private key component of the KeyPair.
Get the public key component of the KeyPair.
Sign a message with this key. message should be either a String or a Buffer, and the returned signature will be a String.
Get your client's NodeID on the Storj network, which is derived from this KeyPair.
Return a bitcoin-format address derived from this KeyPair.
The Low Level API isn't actually that low level. The purpose of these methods is to provide tools that are useful when building production Storj.js applications, but that aren't necessary for casual development. These methods may expose primitives, and often sacrifice usability for perfomance.
Note: The Low Level API is not considered stable yet. Please do not develop against this API unless you are willing to deal with breaking changes in future releases. Until otherwise stated, minor and patch releases may ship breaking cheanges to this API.
Return a readable stream of decrypted data being pulled directly from farmers. This method bypasses the File API entirely, and doesn't use a backend abstract-blob-store. If you only need to download a file once, and don't want to hold onto it in memory, this is the method for you.
storj.download(fileId, bucketId).pipe(fs.createWriteStream('cat.jpg'));Return a writable stream. When written to, the data will be encrypted and uploaded to the storj network.
When it becomes available, stream will emit a done event. This event will contain the metadata for the uploaded file including:
{
bucket: STRING, // bucketId
filename: STRING,
mimetype: STRING,
id: STRING, // fileId
size: NUMBER // Size of file on the network
}fs.createReadStream('cat.jpg').pipe(
storj.upload(fileId, bucketId)
).on('done', function(metadata) {
console.log(`Uploading to id: ${metadata.id}`);
})Get all of the information necessary to download a file from the Storj network. The callback will be inovked with an Error if something goes wrong, otherwise it will return an object of the form:
{
token: [Object], // Information necessary to decrypt files from public buckets
pointers: [Array] // Information necessary to find farmers with shards
}While this method is currently exposed, there is no direct way of instructing the Storj.js API to use this when downloading a file from the network.