` which contains `messageId`, `popReceipt`, `timeNextVisible`, `insertionTime` and `expirationTime`. It can be passed to updateMessage and deleteMessage APIs.
+
+FILE
+* Returned content MD5 for range gets Files.
+* Fixed the issue that `useTransactionalMD5` didn't take effect for downloading a big file.
+* Added support for listing files and directories with prefix, refer to `FileService.listFilesAndDirectoriesSegmentedWithPrefix`.
+
+TABLE
+* Fixed the issue that response in incorrect for table batch operation when the error response item is not the first item in the responses.
+
+2016.11 Version 1.4.0
+
+ALL
+* Added `ENOTFOUND` for secondary endpoint and `ECONNREFUSED` to `RetryPolicyFilter`.
+* Added support for `text/html` error response body.
+
+BLOB
+* Fixed the issue that the ChunkAllocator maxCount is aligned with parallelOperationThreadCount.
+* Changed `/S` of SpeedSummary to `/s`.
+* Fixed the issue that `BlobService.createBlockBlobFromText` will hang when passed `null` or `undefined` `text` argument.
+* Fixed the issue that `BlobService.createBlockBlobFromText` will always set `content-type` to `text/plain`.
+
+QUEUE
+* Allowed `QueueService.peekMessages` against secondary endpoint.
+
+FILE
+* Fixed the issue that the ChunkAllocator maxCount is aligned with parallelOperationThreadCount.
+* Changed `/S` of SpeedSummary to `/s`.
+
+2016.10 Version 1.3.2
+
+BLOB
+* Prevent a blockId from being generated with a decimal point.
+
+2016.09 Version 1.3.1
+
+ALL
+* Improved the type script support.
+
+2016.08 Version 1.3.0
+
+ALL
+
+* Fixed the issue that retry filter will fail against storage emulator.
+* Fixed a hang issue of `StorageServiceClient` with retry policy filter set when retrying sending the request, the stream is not readable anymore.
+* Updated the default value of `CorsRule.ExposedHeaders`, `CorsRule.AllowedHeaders` to empty and `CorsRule.MaxAgeInSeconds` to `0` for `setServiceProperties` APIs of all services.
+* Fixed the issue that service SAS doesn't work if specifying the `AccessPolicy.Protocols`.
+
+BLOB
+* Added the API `BlobService.getPageRangesDiff` for getting the page ranges difference. Refer to https://msdn.microsoft.com/en-us/library/azure/mt736912.aspx for more detailed information.
+
+QUEUE
+* Updated the `QueueMessageResult.dequeueCount` from `string` to `number`.
+* Added the API `QueueService.getUrl` for getting the queue url.
+
+TABLE
+* Added the API `TableService.getUrl` for getting the table url.
+
+2016.07 Version 1.2.0
+
+ALL
+* Fixed the issue that metadata name will be converted to lower-case after retrieving back from the server. **Note** that this fix is only applicable for Node 0.12 or higher version.
+* Added support for EndpointSuffix for all service constructors.
+* Updated storage service version to 2015-12-11. Fore more information, please see - https://msdn.microsoft.com/en-us/library/azure/dd894041.aspx
+* Updated the `request` package to version 2.74.0 to address the security vulnerability - https://nodesecurity.io/advisories/130
+
+BLOB
+* Fixed the issue that the service error message will be written to the destination stream if getting error when downloading the blob to a stream/file.
+* Added `serverEncryped` property to `BlobResult` class which indicates if the blob data and application metadata are completely encrypted using the specified algorithm on the server.
+
+FILE
+* Fixed the issue that the service error message will be written to the destination stream if getting error when downloading the file to a stream/file.
+
+TABLE
+* The atom feed payload format is not supported anymore for table service APIs.
+
+2016.06 Version 1.1.0
+
+ALL
+* Fixed the issue that using SAS doesn't work against storage emulator.
+* Fixed the issue that the service SAS signature is incorrect when protocol parameter is specified.
+* Fixed the issue that the timeout query string should be in seconds instead of milliseconds.
+
+BLOB
+* Added parameter snapshotId to BlobService.getUrl function to support getting url of a specified snapshot.
+* Fixed the issue that the getUrl doesn't work against storage emulator.
+* Fixed the race issue that the _rangeList may be deleted before using it in the BlockRangeStream._getTypeList function.
+* Fixed the issue that downloading block blob with size bigger than 32MB will fail when using anonymous credential.
+* Added `CREATE` to `BlobUtilities.SharedAccessPermissions`.
+
+TABLE
+* Supported string type value for entity PartionKey and RowKey.
+* Supported implicit Edm type value for entity properties. The supported implicit Edm types including Int32, Double, Bool, DateTime and String.
+
+FILE
+* Fixed the issue that the getUrl doesn't work against storage emulator.
+* Added `CREATE` to `FileUtilities.SharedAccessPermissions`.
+
+2016.05 Version 1.0.1
+
+ALL
+* Fixed the issue that StorageServiceClient._normalizeError will throw exception on Node below v4 because string.startsWith is not available on Node below v4.
+
+2016.05 Version 1.0.0
+
+BLOB
+* The `blob` property of BlobResult has been renamed to `name` to keep consistent with other services API and the `listBlob` API.
+* Decoded the block name of LockListResult from base64 string to utf-8 string.
+
+QUEUE
+* The `encodeMessage` flag of QueueService has been replaced by `messageEncoder` which support `TextBase64QueueMessageEncoder`, `BinaryBase64QueueMessageEncoder`, `TextXmlQueueMessageEncoder` and custom implementation of QueueMessageEncoder.
+
+TABLE
+* Fixed the issue that loses the data type for Edm.Double value like: 1.0.
+* Fixed the issue that loses the data precision for Edm.Int64 value when it is outisde of the range (2^53 - 1) to -(2^53 - 1).
+
+2016.03 Version 0.10.0
+
+ALL
+* The `signedIdentifiers` parameter and result properties have been changed from array to hash map to avoid non unique signed identifier id.
+
+BLOB
+* Added 'COPY' to the BlobUtilities.BlobListingDetails to include copy information in the results.
+* Added 'bytesCopied' and 'totalBytes' to the blob result.
+* Added the blob result to the callback of BlobService.commitBlocks.
+* Moved the properties in the properties object of BlobResult and ContainerResult when listing blobs or containers to the result object.
+* Renamed the property names returned from listing blobs or containers to camelCase.
+* The `contentType`, `contentEncoding`, `contentLanguage`, `contentDisposition`, 'contentMD5' and `cacheControl` parameters and return values about the blob's content settings are grouped into a `contentSettings` sub property.
+* The `contentMD5` parameter to verify the integrity of the data during the transport is changed to `transactionalContentMD5`
+* The `copy*` return values are grouped into a `copy` sub property.
+* The `lease*` return values are grouped into a `lease` sub property.
+* The options.accessConditions parameter is changed to AccessConditions type.
+
+QUEUE
+* Renamed QueueResult.approximatemessagecount to camelCase and change its type to 'number.
+* Renamed the property names of QueueMessageResult to camelCase.
+* Renamed the parameter options.messagettl of the createMessage API to options.messageTimeToLive.
+* Updated the callback of the createMessage API from errorOrResult to errorOrResponse.
+* Removed peekOnly option from the options parameter of the getMessages API. To peek messages, use peekMessages instead.
+* Added getMessage and peekMessage API.
+
+FILE
+* Moved the properties in the properties object of FileResult and ShareResult when listing files or shares to the result object.
+* Renamed the property names returned from listing files or shares to camelCase.
+* Renamed the property names returned from getting share stats to camelCase.
+* The `contentType`, `contentEncoding`, `contentLanguage`, `contentDisposition`, 'contentMD5' and `cacheControl` parameters and return values about the blob's content settings are grouped into a `contentSettings` sub property.
+* The `contentMD5` parameter to verify the integrity of the data during the transport is changed to `transactionalContentMD5`
+* The `copy*` return values are grouped into a `copy` sub property.
+* Fixed the issue that SAS tokens created from table names with upper-case letters do not work.
+* The options.accessConditions parameter is changed to AccessConditions type.
+
+TABLE
+* Fixed the issue that getTableAcl returns empty array with signedIdentifier property.
+* Renamed the function updateEntity to replaceEntity.
+* Renamed TableUtilities.entityGenerator.Entity to EntityProperty.
+
+2016.03 Version 0.9.0
+
+ALL
+* Updated storage service version to 2015-04-05. Fore more information, please see - https://msdn.microsoft.com/en-us/library/azure/dd894041.aspx
+* Added support for Account SAS.
+* Added support for IPACL and Protocols options for service SAS.
+* Fixed the issue where the authentication may fail when a metadata key is in upper case.
+* Added 'nsp check' task for security vulnerability check.
+* Updated the dependency of the 'request' module to avoid the security vulnerability reported by the 'nsp' tool.
+
+BLOB
+* Added new permission 'ADD' for service SAS.
+
+FILE
+* Added support for metrics setting for service properties.
+
+2016.01 Version 0.8.0
+
+ALL
+* Preview release of the TypeScript definition file at "lib/azure-storage.d.ts".
+
+BLOB
+* Added the blob result to the callback of BlobService.commitBlocks.
+* Added the speed summary to the downloading APIs.
+
+2015.12 Version 0.7.0
+
+ALL
+* Fixed the typo in the function generateDevelopmentStorageCredentials.
+* Fixed the issue that the HTTP global agent setting is changed during parallel uploading and downloading and impacts on other Node.js applications.
+* Fixed the issue that the chunked stream writing methods do not accept string.
+* Fixed the issue that the request fails when the content-length is set to string '0' in the 'sendingRequestEvent' event handler.
+* Supported retry on XML parsing errors when the XML in the response body is corrupted.
+* Replaced the dependency "mime" to "browserify-mime" to work with Browserify.
+
+BLOB
+* Added an option to skip the blob or file size checking prior to the actual downloading.
+* Fixed the issue that it doesn't callback when loses the internet connection during uploading/uploading.
+* Fixed the issue that the local file cannot be removed in the callback when uploading a blob from a local file.
+* Fixed the issue that the stream length doesn't work when it is larger than 32MB in the createBlockBlobFromStream, createPageBlobFromStream, createAppendBlobFromStream and appendFromStream functions.
+* Fixed the issue that it doesn't return error in the page range validation when the size exceeds the limit.
+* Renamed the function AppendFromLocalFile to appendFromLocalFile.
+* Renamed the function AppendFromStream to appendFromStream.
+* Renamed the function AppendFromText to appendFromText.
+
+TABLE
+* Fixed the issue that listTablesSegmentedWithPrefix with maxResult option throws exception.
+
+2015.09 Version 0.6.0
+
+ALL
+* Fixed the MD5 mismatch issue in uploading a blob when running with Node.js v4.0 or io.js.
+
+BLOB
+* Fixed the issue that it doesn't prompt appropriate error message when the source URI is missing in BlobService.startCopyBlob().
+
+2015.08 Version 0.5.0
+
+ALL
+* Updated storage service version to 2015-02-21. For more information, please see - https://msdn.microsoft.com/en-us/library/azure/dd894041.aspx
+* Unified the function parameters for setting ACL of container, table, queue and share.
+* Renamed 'AccessPolicy.Permission' to 'AccessPolicy.Permissions' on the result object from get*Acl to match the property name on the signedIdentifier property passed to set*Acl calls.
+* Unified the name pattern of the http header constants.
+* Split the property parameters from the options parameter for setting properties of blob, share and file.
+* Updated the error message when an argument is in a wrong type while it requires a string.
+* Exported AccessCondition to generate an object that represents a condition.
+* Fixed an issue that the SAS in the SharedAccessSignature part of the connection string cannot start with '?'.
+* Deprecated the generateSharedAccessSignatureWithVersion() method in each service.
+
+BLOB
+* Supported operating against append blobs.
+* Fixed an issue that the file descriptor in the FileReadStream is not closed.
+
+QUEUE
+* Fixed an issue that options.messageText doesn't work in QueueService.updateMessage.
+
+2015.06 Version 0.4.5
+
+* Updated the dependency of the 'request' module to avoid the security vulnerability reported by the 'nsp' tool: (https://nodesecurity.io/advisories/qs_dos_extended_event_loop_blocking) and (https://nodesecurity.io/advisories/qs_dos_memory_exhaustion).
+* Included package validation in grunt tasks.
+
+2015.05 Version 0.4.4
+
+ALL
+* Updated the dependency of the 'validator' module to avoid the security vulnerability reported by the 'nsp' tool. (https://nodesecurity.io/advisories/validator-isurl-denial-of-service)
+* Updated the error message when an argument is in a wrong type while it requires a string.
+* Updated the grunt file to run test with mocha and generate jsDoc.
+
+BLOB
+* Fixed an issue that the metadata is duplicated when creating a page blob.
+* Fixed an issue that the metadata is duplicated when setting blob's metadata with metadata in the options.
+* Fixed an issue that cannot create an empty block blob with useTransactionalMD5 option.
+
+FILE
+* Fixed an issue that the result of file downloading contains wrong values for share, directory or file names.
+
+TABLE
+* Fixed an issue that it prompts "Cannot set property 'isSuccessful' of null" when TableService.createTableIfNotExists is called.
+
+2015.03 Version 0.4.3
+
+ALL
+* Fixed an issue that setting metadata keys are converted into lowercase. The metadata keys retrieved from the service will however still be converted into lowercase by the http component of Node.js.(https://github.com/joyent/node/issues/1954)
+* Included all storage error code strings in the error constants definition.
+* Documented the client request ID option in all APIs.
+
+BLOB
+* Supported listing blob virtual directories.
+* Fixed an issue that exception is thrown when downloading a blob larger than 32MB to a stream.
+* Fixed an issue that the process exits when the free memory is low.
+
+2014.12 Version 0.4.2
+
+ALL
+* Fixed an issue that batch operation could probably wait without callback.
+* Added the readable-stream module to adapt stream operations in both node 0.8 and node 0.10.
+* Supported nock in tests.
+
+BLOB
+* Supported trimming the default port of http or https when getting URL for the blob service.
+* Fixed an issue that the metadata is not populated when getting the blob to text.
+
+FILE
+* Supported trimming the default port of http or https when getting URL for the file service.
+
+2014.11.28 Version 0.4.1
+
+ALL
+* Fixed an issue where the request does not invoke the callback when the input stream ends with an 'end' event instead of a 'finish' event.
+* Fixed an issue where the request does not invoke the callback when the input stream ends with a 'close' event on Node 0.8.X.
+* Fixed an issue that the temporary files generated by unit tests are not cleaned up.
+* Fixed an issue that the unit tests may fail when the file generated by previous tests is not accessible temporarily.
+
+FILE
+* Added support to download a single file in parallel similar to upload. You can set ‘parallelOperationThreadCount’ option for api’s that download a file to indicate number of parallel operations to use for download.
+
+TABLE
+* Fixed an issue which caused invalid input errors when the partition key or the row key contains an apostrophe.
+
+2014.10.28 Version 0.4.0
+
+ALL
+* Provide an option to enable/disable nagling. Nagling is disabled by default. It can be enabled by setting options.useNagleAlgorithm to true.
+* Added batch operation callback in sequence mode.
+
+BLOB
+* Added support to download a single blob in parallel similar to upload. You can set ‘parallelOperationThreadCount’ option for api’s that download a blob to indicate number of parallel operations to use for download.
+* Added speed summary in blob downloading.
+
+FILE
+* Fixed an issue which caused an invalid resource name error when the directory name starts or ends with a '/'
+
+2014.08.20 Version 0.3.3
+
+BLOB
+* Fixed an issue where SAS tokens were being incorrectly generated for the root container and when the blob name required encoding.
+* Documented the 'parallelOperationThreadCount' option as input to various uploadBlob APIs.
+
+FILE
+* Fixed an issue where signing was incorrect when the URI contained '.' or '..'.
+* Fixed an issue where "getURI" was requiring a file parameter, although the parameter should be optional.
+
+2014.07.25 Version 0.3.2
+
+ALL
+* Fixed an issue which prevented transient server errors like ECONNRESET, ESOCKETTIMEDOUT and ETIMEDOUT from being retried.
+
+BLOB
+* Fixed an issue which caused a reference error in blobs due to 'err' not being defined.
+
+2014.07.22 Version 0.3.1
+
+ALL
+* Fixed an issue which failed to validate special names for containers and tables.
+* Exposed the Validation utility methods so users can use it to validate resource names.
+
+BLOB
+* Fixed an issue which caused failures when an error was encountered while uploading big blobs.
+
+2014.07.07 Version 0.3.0
+
+BLOB
+* Fixed an issue which failed to return single item blocklists while doing listBlocks.
+
+FILE
+* Added File Service support. The File Service and the associated APIs are in preview.
+
+2014.07.01 Version 0.2.1
+
+ALL
+* Fixed an issue with casing which caused the module to fail on linux machines.
+
+BLOB
+* Fixed an issue which failed to upload an empty blob for empty block blob files uploaded using createBlockBlobFromFile when retry policies were used.
+
+2014.06.16 Version 0.2.0
+
+ALL
+* Updated storage service version to 2014-02-14. The SAS tokens generated will therefore contain a signed version of 2014-02-14 and all the requests using SAS credentials have the api-version query parameter appended to the URI.
+
+2014.06.12 Version 0.1.0
+
+ALL
+* The package has been renamed to azure-storage.
+* There is no separate azure-common sub-package. Everything is condensed into a single package called azure-storage.
+* azure.create*Service supports the following configurations:
+ * create*Service(connection string)
+ * create*Service(account name, account key)
+ * create*Service(storage host, sasToken)
+* Added the ability to choose which SAS Version to use when generating Shared Access Signatures (either the 2012-02-12 or 2013-08-15 versions).
+* Host can be given as either an object with primaryHost and secondaryHost or as a string representing the primary.
+* The order credentials are assessed is consistent: If parameters are passed in, they and they alone are honored. There is no mixing (ex, if users pass in host, they won't get the access key from your env var). If no parameters are passed in, the env vars are used. Within both those strategies, the order of evaluation is emulator (in the case of EMULATED env var only), connection string, account/key or SAS, anonymous. If account/key and SAS are passed in, an error is thrown indicating the credentials are invalid.
+* Removed the ability to create a storage service from a config file.
+* azure.create*Service supports secondaryHost only, but either primaryHost or secondaryHost must be provided.
+* Storage service client constructors take the sasToken rather than a credentials object, meaning that the SharedAccessSignature class no longer needs to be used by consumers.
+* Ensure request is always built/signed for every retry attempt.
+* Custom retry policies should implement the shouldRetry method and return an object with the retryInterval and retryable information in it. Optionally, they can also set the locationMode and targetLocation to which the request should be sent.
+* Implemented RA-GRS support. For more information on this, please see - http://blogs.msdn.com/b/windowsazurestorage/archive/2013/12/04/introducing-read-access-geo-replicated-storage-ra-grs-for-windows-azure-storage.aspx
+* Service properties updated: replaced metrics with hour metrics and minute metrics, added cors support, added defaults if properties are unspecified to reduce invalid xml exceptions.
+* Added maximum execution time, settable for all requests via {blob|queue|table}service.defaultMaximumExecutionTime or for an individual request via options.maximumExecutionTime. This applies to all requests except blob downloads.
+* The blob, queue and table services no longer set/modify any values within the options object optionally passed in by the user for every API.
+* Fixed an issue where null, empty and white-space only metadata header values were allowed.
+* "timeout" query parameter will not be sent to the server if not set by the user. In order to set the timeout per API, please use options.timeoutIntervalInMs. To set it for all requests made via a particular service, please use {blob|queue|table}Service.defaultTimeoutIntervalInMs.
+* ECONNRESET is handled in the retry policy filter.
+* DevStore with secondary access is supported.
+* Set*Acl takes signed identifiers as a parameter - before it was in options.
+* GenerateSharedAccessSignature() produces a query string rather than an object.
+* The SharedKey class has the methods to create shared access signatures. These should not be in the SharedAccessSignature class because one can only create a SAS if they have the account/key.
+* The service client no longer evaluates the port and protocol set on it. Before, if storageserviceclient.host was called and port and protocol had been changed after host was set, host would be incorrect.
+* Removed SharedKeyLite and SharedKeyLiteTable in favor of SharedKey and SharedKeyTable which were already the defaults.
+* Added separate utility files for Blob, Queue, Table, and Storage. These contain useful enums that were previously found in a single Constants file as well as new utility functions. The old Constants file will mostly include internal-use constants.
+
+BLOB
+* createBlobServiceWithSas has been provided to create a blobService to use with a Shared Access Signature. Users can create a blobService using azure.createBlobServiceWithSas(host, sasToken).
+* Anonymous access for the blob service is supported.
+* Added support for 2013-08-15 Blob SAS changes.
+* Renamed listBlobs to listBlobsSegmented and added listBlobsSegmentedWithPrefix. listBlobsSegmented takes in currentToken and listBlobsSegmentedWithPrefix takes in prefix and currentToken along with other parameters. Please look at the documentation of these APIs for a list of parameters that users can set on the options object. These APIs return only error, result and response. The result contains entries which is a list of blobs and a continuation token for successive listing operations.
+* Renamed copyBlob to startCopyBlob.
+* Renamed putBlockBlobFromStream to _putBlockBlobFromStream and putBlockBlobFromFile to _putBlockBlobFromFile. These are internal methods and should not be called by users directly. Please use createBlockBlobFromStream and createBlockBlobFromFile.
+* Renamed page methods: listBlobRegions to listPageRanges, createBlobPagesFromText to createPagesFromText, clearBlobPages to clearPageRanges.
+* Renamed block methods: createBlobBlockFromStream to createBlockFromStream, createBlobBlockFromText to createBlockFromText, commitBlobBlocks to commitBlocks, listBlobBlocks to listBlocks.
+* BlobService lease methods also work with container leases, simply specify null for the blob parameter.
+* Added changeLease method to modify the lease ID of an active lease.
+* Fixed lease issues, break lease allows a leaseBreakPeriod of 0, lease time header is returned as an int rather than a string.
+* Added snapshot delete options: when deleting a blob with snapshots, users can decide to delete blob and snapshots or just snapshots. The options are provided in BlobUtilities.SnapshotDeleteOptions.*.
+* deleteBlob callback does not return isSuccessful.
+* Added does{Container|Blob}Exist methods in blobservice that can be used to determine if a particular container or blob exists.
+* Added delete{Container|Blob}IfExists methods in blobservice that can be used to delete a container or a blob only when they exist.
+* Added ContentMD5 validation for blob downloads. This is turned on by default for all block blob downloads and all page blob range downloads as long as the range is less than 4MB. In order to turn this off, set options.disableContentMD5Validation to true explicitly.
+* x-ms-range-get-content-md5 is set internally by the library and users do not have to specify it in the options.
+* Removed the option of doing range downloads while downloading a blob to text.
+* Added sequence number support for page blobs. Users can set the sequence number of a page blob using blobService.setPageBlobSequenceNumber and manage concurrency issues using x-ms-if-sequence-number-le, x-ms-if-sequence-number-lt and x-ms-if-sequence-number-eq. Please see http://msdn.microsoft.com/en-us/library/azure/ee691975.aspx for more details about using sequence numbers.
+* Removed createBlob API. Please use createPageBlob and createBlockBlob* APIs to create the respective blobs.
+* Renamed createPagesFromText to _createPagesFromText. This is an internal method and should not be called by users directly.
+* Added resizePageBlob that can be used to resize a page blob.
+* createPageBlob takes in the blob's sequence number using options.sequenceNumber.
+* All the BlobService APIs that took cacheControl/cacheControlHeader, contentType/contentTypeHeader, contentEncoding/contentEncodingHeader, contentLanguage/contentLanguageHeader, contentMD5/contentMD5Header in options only take cacheControl, contentType, contentEncoding, contentLanguage and contentMD5. These are the values that will be set on the blob at the server.
+* createPagesFromStream takes in the following 2 options - useTransactionalMD5 to calculate and send/validate content MD5 for each transaction and contentMD5 which is an optional hash value. When contentMD5 is provided, the client library uses that instead of trying to calculate it based on the data being uploaded.
+* createBlockBlobFromText, createBlockFromStream and createBlockFromText allows users to set useTransactionalMD5 on options to calculate and send/validate content MD5 for each transaction.
+* Added createWriteStreamToBlockBlob, createWriteStreamToNewPageBlob and createWriteStreamToExistingPageBlob that provide a stream for writing to the blob.
+* Added createReadStream that provides a stream for reading from the blob.
+* blobService can have a default parallelOperationThreadCount which specifies the number of parallel upload operations that may be performed when uploading a blob that is greater than the value specified by singleBlobPutUploadThresholdInBytes. This value can be set using blobService.parallelOperationThreadCount. The default value set on blobService is 1.
+* createBlockBlobFromText supports text Buffers in addition to strings.
+* createBlockBlobFromText will throw an error if the uploaded content exceeds 64MB.
+* BlobService getBlobUrl has been renamed to getUrl as it can also produce container urls. It can no longer create a SAS token (it used to take sharedAccessPolicy) but can take a sasToken produced by the generateSharedAccessSignature method and produce a url with that.
+
+QUEUE
+* Added Shared Access Signatures for queues. createQueueServiceWithSas has been provided to create a queueService to use with a Shared Access Signature. Users can create a queueService using azure.createQueueServiceWithSas(host, sasToken).
+* Renamed listQueues to listQueuesSegmented and added listQueuesSegmentedWithPrefix. listQueuesSegmented takes in currentToken and listQueuesSegmentedWithPrefix takes in prefix and currentToken along with other parameters. Please look at the documentation of these APIs for a list of parameters that users can set on the options object. These APIs return only error, result and response. The result contains entries which is a list of queues and a continuation token for successive listing operations.
+* deleteQueue and deleteMessage callbacks do not return isSuccessful.
+* Added an option in the queue service to turn base 64 encoding off.
+
+TABLE
+* Added Shared Access Signatures for tables. createTableServiceWithSas has been provided to create a tableService to use with a Shared Access Signature. Users can create a tableService using azure.createTableServiceWithSas(host, sasToken).
+* Added JSON support for tables and removed AtomPub. For the different flavours of JSON supported, please see - http://blogs.msdn.com/b/windowsazurestorage/archive/2013/12/05/windows-azure-tables-introducing-json.aspx.
+* Renamed queryTables to listTablesSegmented and added listTablesSegmentedWithPrefix. listTablesSegmented takes in currentToken and listTablesSegmentedWithPrefix takes in prefix and currentToken along with options and callback. Please look at the documentation of these APIs for a list of parameters that users can set on the options object. These APIs return only error, result and response. The result contains entries which is a list of tables and a continuation token for successive listing operations.
+* deleteTable and deleteEntity callbacks do not return isSuccessful.
+* queryEntities in TableService returns 3 parameters instead of 4: the entities and queryResultContinuation parameters are returned within a queryResult object.
+* Added support for disabling echo content in inserts. By default, inserts do not echo content.
+* Changed table error parsing so that the code string and message string are directly accessible from the error object.
+* Removed the getTable method; doesTableExist works similarly.
+* createTable does not request content back from the service, but still returns an object containing the TableName.
+* Renamed queryEntity in TableService to retrieveEntity.
+* Modified how batches work. Instead of turning the service batch mode on/off, a batch is a separate entity like query. Batches are constructed and then executed.
+* queryEntities in TableService requires a continuation token.
+* TableService updateEntity, mergeEntity and deleteEntity do not take a checkEtag option. The entity's etag is sent if it exists, otherwise * is sent.
+* retrieveEntity and queryEntities accept empty partition and row keys.
+* Added entity-property-creation helper methods. Users can use the entityGenerator provided in TableUtilities and create entity properties as follows:
+ var entGen = TableUtilities.entityGenerator;
+ var entity = { PartitionKey: entGen.String('part2'),
+ RowKey: entGen.String('row1'),
+ boolValueTrue: entGen.Boolean(true),
+ boolValueFalse: entGen.Boolean(false),
+ intValue: entGen.Int32(42),
+ dateValue: entGen.DateTime(new Date(Date.UTC(2011, 10, 25))),
+ complexDateValue: entGen.DateTime(new Date(Date.UTC(2013, 02, 16, 01, 46, 20)))
+ };
+* Removed TableQuery whereKeys method. Instead of tableQuery.whereKeys, tableService.retrieveEntity should be used.
+* Removed TableQuery whereNextKeys method. Instead of tableQuery.whereNextKeys, tableService.queryEntities takes currentToken which can be retrieved from a previous queryEntities call in results.
+* Removed TableQuery from method. Instead of tableQuery.from, tableService.queryEntities takes table and tableQuery may be null to represent retrieving all entities in the table.
+* TableQuery select is an instance method for consistency with top and where. Instead of TableQuery.select('foo'), use new TableQuery().select('foo').
+* TableQuery provides helper methods to create filter strings to use with the where clause for a query. Query strings may also include type specifiers where necessary.
+ For example, to query on a long value, users could do the following:
+ var tableQuery = new TableQuery().where(TableQuery.int64Filter('Int64Field', TableUtilities.QueryComparisons.EQUAL, '4294967296'));
+ OR
+ var tableQuery = new TableQuery().where('Int64Field == ?int64?', '4294967296');
+
+2013.01.15 Version 0.8.0
+* Added the Preview Service Management libraries as separate modules
+* Added ability to consume PEM files directly from the Service Management libraries
+* Added support for createOrUpdate and createRegistrationId in the Notification Hubs libraries
+
+2013.01.10 Version 0.7.19
+* Lock validator version
+
+2013.11.27 Version 0.7.18
+* Lock xmlbuilder version
+
+2013.11.5 Version 0.7.17
+* Added getBlob and createBlob operations that support stream piping
+* Added compute, management, network, serviceBus, sql, storage management, store and subscription preview wrappers
+* Multiple bugfixes
+
+2013.10.16 Version 0.7.16
+* Improved API documentation
+* Updated Virtual Machines API to 2013-06-01
+* Added website management preview wrappers
+* Multiple bugfixes
+
+2013.08.19 Version 0.7.15
+* Multiple storage fixes
+* Fix issue with Notification Hubs template message sending
+
+2013.08.12 Version 0.7.14
+* Multiple storage fixes
+* Documentation improvements
+* Added support for large blobs upload / download
+
+2013.08.08 Version 0.7.13
+* Lock request version
+
+2013.07.29 Version 0.7.12
+* Added MPNS support
+* Added Service management vnet operations support
+
+2013.07.10 Version 0.7.11
+* Hooked up new configuration system to storage APIs
+* Support for AZURE_STORAGE_CONNECTION_STRING environment variable
+* Included API for websites management
+* Fixed UTF-8 support in table batch submit
+
+2013.06.26 Version 0.7.10
+* Various fixes in storage APIs
+
+2013.06.19 Version 0.7.9
+* First part of new SDK configuration system
+* Support for AZURE_SERVICEBUS_CONNECTION_STRING environment variable
+* Updated SAS generation logic to include version number
+* Infrastructure support for creating passwordless VMs
+
+2013.06.13 Version 0.7.8
+* Updates to HDInsight operations
+
+2013.06.06 Version 0.7.7
+* Added support for Android notification through Service Bus Notification Hubs
+* Support prefixes when listing tables
+* Support '$logs' as a valid blob container name to support reading diagnostic information
+* Fix for network configuration serialization for subnets
+
+2013.05.30 Version 0.7.6
+* Added list, delete and create cluster operations for HD Insight.
+
+2013.05.15 Version 0.7.5
+* Fixed registration hubs issue with requiring access key when shared key was provided.
+* Fixed registration hubs issue with listByTag, Channel and device token
+
+2013.05.09 Version 0.7.4
+* Fixed encoding issue with partition and row keys in table storage query
+
+2013.05.01 Version 0.7.3
+* Fixed issue #680: BlobService.getBlobUrl puts permissions in SAS url even if not given
+* Changes to test suite & sdk to run in other environments
+* Notification hubs registrations
+* Support in ServiceManagementClient for role reboot and reimage
+
+2013.04.05 Version 0.7.2
+* Removing workaround for SSL issue and forcing node version to be outside the > 0.8 && < 0.10.3 range where the issue occurs
+
+2013.04.03 Version 0.7.1
+* Adding (limited) support for node 0.10
+* Fixing issue regarding registering providers when using websites or mobiles services
+
+2013.03.25 Version 0.7.0
+* Breaking change: Primitive types will be stored for table storage.
+* Adding support for creating and deleting affinity groups
+* Replacing http-mock by nock and making all tests use it by default
+* Adding notification hubs messages for WNS and APNS
+* Add Strict SSL validation for server certificates
+* Add support for creating subscriptions that expire
+
+2013.03.12 Version 0.6.11
+* Added constraint to package.json to restrict to node versions < 0.9.
+
+2013.02.11 Version 0.6.10
+* Added helper date.* functions for generating SAS expirations (secondsFromNow, minutesFromNow, hoursFromNow, daysFromNow)
+* Added SQL classes for managing SQL Servers, Databases and Firewall rules
+* Updating to use latest xml2js
+
+2012.12.12 Version 0.6.9
+* Exporting WebResource, Client classes from package to support CLI.
+* Install message updated to remind users the CLI is now a separate package.
+
+2012.11.20 Version 0.6.8
+ * CLI functionality has been pulled out into a new "azure-cli" module. See https://github.com/WindowsAzure/azure-sdk-tools-xplat for details.
+ * Add support for sb: in ServiceBus connection strings.
+ * Add functions to ServiceManagement for managing storage accounts.
+ * Merged #314 from @smarx for allowing empty partition keys on the client.
+ * Merged #447 from @anodejs for array enumeration and exception on batch response.
+ * Various other fixes
+
+2012.10.15 Version 0.6.7
+ * Adding connection strings support for storage and service bus
+ * Fixing issue with EMULATED and explicit variables making the later more relevant
+ * Adding Github support
+ * Adding website application settings support
+
+2012.10.12 Version 0.6.6
+ * Using fixed version of commander.js to avoid bug in commander.js 1.0.5
+
+2012.10.01 Version 0.6.5
+ * Bugfixing
+
+2012.09.18 Version 0.6.4
+ * Multiple Bugfixes around blob streaming
+
+2012.09.09 Version 0.6.3
+ * Fixing issue with xml2js
+
+2012.08.15 Version 0.6.2
+ * Multiple Bugfixes
+
+2012.07.02 Version 0.6.1
+ * Multiple Bugfixes
+ * Adding subscription setting and listing functionality.
+
+2012.06.06 Version 0.6.0
+ * Adding CLI tool
+ * Multiple Bugfixes
+
+2012.04.19 Version 0.5.3
+ * Service Runtime Wrappers
+ * Multiple Bugfixes
+ * Unit tests converted to mocha and code coverage made easy through JSCoverage
+
+2012.02.10 Version 0.5.2
+ * Service Bus Wrappers
+ * Storage Services UT run against a mock server.
+ * Node.exe version requirement lowered to raise compatibility.
+ * Multiple Bugfixes
+
+2011.12.14 Version 0.5.1
+ * Multiple bug fixes
+
+2011.12.09 Version 0.5.0
+ * Initial Release
diff --git a/src/node_modules/azure-storage/ISSUE_TEMPLATE.md b/src/node_modules/azure-storage/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000..dba6d32
--- /dev/null
+++ b/src/node_modules/azure-storage/ISSUE_TEMPLATE.md
@@ -0,0 +1,16 @@
+### Which service(blob, file, queue, table) does this issue concern?
+
+
+### Which version of the SDK was used?
+
+
+### What's the Node.js/Browser version?
+
+
+### What problem was encountered?
+
+
+### Steps to reproduce the issue?
+
+
+### Have you found a mitigation/solution?
diff --git a/src/node_modules/azure-storage/LICENSE.txt b/src/node_modules/azure-storage/LICENSE.txt
new file mode 100644
index 0000000..21254fc
--- /dev/null
+++ b/src/node_modules/azure-storage/LICENSE.txt
@@ -0,0 +1,176 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/README.md b/src/node_modules/azure-storage/README.md
new file mode 100644
index 0000000..3cd96db
--- /dev/null
+++ b/src/node_modules/azure-storage/README.md
@@ -0,0 +1,560 @@
+# Microsoft Azure Storage SDK for Node.js and JavaScript for Browsers
+
+[](http://badge.fury.io/js/azure-storage)
+
+* Master [](https://travis-ci.org/Azure/azure-storage-node/branches) [](https://coveralls.io/github/Azure/azure-storage-node?branch=master)
+* Dev [](https://travis-ci.org/Azure/azure-storage-node/branches) [](https://coveralls.io/github/Azure/azure-storage-node?branch=dev)
+
+This project provides a Node.js package and a browser compatible [JavaScript Client Library](https://github.com/Azure/azure-storage-node#azure-storage-javascript-client-library-for-browsers) that makes it easy to consume and manage Microsoft Azure Storage Services.
+
+> This README page is a reference to the SDK v2. For the new SDK v10, go to [Storage SDK v10 for JavaScript](https://github.com/Azure/azure-storage-js).
+
+| SDK Name | Version | Description | NPM/API Reference Links |
+|------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [Storage SDK v10 for JavaScript](https://github.com/Azure/azure-storage-js) | v10 | The next generation Storage SDK (Blob/Queue/File, async and promise support) | [NPM](https://www.npmjs.com/package/@azure/storage-blob) - [Reference](https://docs.microsoft.com/en-us/javascript/api/overview/azure/storage/client?view=azure-node-preview) |
+| [Storage SDK v2 for JavaScript](https://github.com/Azure/azure-storage-node) | v2 | Legacy Storage SDK in this repository (Blob/Queue/File/Table, callback style) | [NPM](https://www.npmjs.com/package/azure-storage) - [Reference](https://docs.microsoft.com/en-us/javascript/api/azure-storage/?view=azure-node-latest) |
+| [Azure Management SDKs for JavaScript](https://github.com/Azure/azure-sdk-for-node) | v2 | Management SDKs including Storage Resource Provider APIs | [NPM](https://www.npmjs.com/package/azure) - [Reference](https://github.com/Azure/azure-sdk-for-node#documentation) |
+
+# Features
+
+- Blobs
+ - Create/Delete Containers
+ - Create/Read/Update/Delete Blobs
+- Tables
+ - Create/Delete Tables
+ - Query/Create/Read/Update/Delete Entities
+- Files
+ - Create/Delete Shares
+ - Create/Delete Directories
+ - Create/Read/Update/Delete Files
+- Queues
+ - Create/Delete Queues
+ - Insert/Peek Queue Messages
+ - Advanced Queue Operations
+- Service Properties
+ - Get Service Properties
+ - Set Service Properties
+
+Please check details on API reference documents:
+
+* [Microsoft official API document on docs.microsoft.com](https://docs.microsoft.com/en-us/javascript/api/azure-storage/?view=azure-node-latest)
+* [Generated API references on GitHub pages](http://azure.github.io/azure-storage-node)
+
+# Getting Started
+
+## Install
+
+```shell
+npm install azure-storage
+```
+
+## Usage
+
+```Javascript
+var azure = require('azure-storage');
+```
+
+When using the Storage SDK, you must provide connection information for the storage account to use. This can be provided using:
+
+* Environment variables - **AZURE_STORAGE_ACCOUNT** and **AZURE_STORAGE_ACCESS_KEY**, or **AZURE_STORAGE_CONNECTION_STRING**.
+
+* Constructors - For example, `var tableSvc = azure.createTableService(accountName, accountKey);`
+
+### Blob Storage
+
+The **createContainerIfNotExists** method can be used to create a
+container in which to store a blob:
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+blobService.createContainerIfNotExists('taskcontainer', {
+ publicAccessLevel: 'blob'
+}, function(error, result, response) {
+ if (!error) {
+ // if result = true, container was created.
+ // if result = false, container already existed.
+ }
+});
+```
+
+To upload a file (assuming it is called task1-upload.txt and it is placed in the same folder as the script below), the method **createBlockBlobFromLocalFile** can be used.
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+
+blobService.createBlockBlobFromLocalFile('mycontainer', 'taskblob', 'task1-upload.txt', function(error, result, response) {
+ if (!error) {
+ // file uploaded
+ }
+});
+```
+
+
+For page blobs, use **createPageBlobFromLocalFile**. There are other methods for uploading blobs also, such as **createBlockBlobFromText** or **createPageBlobFromStream**.
+
+There are also several ways to download block and page blobs. For example, **getBlobToStream** downloads the blob to a stream:
+
+```Javascript
+var blobService = azure.createBlobService();
+var fs = require('fs');
+blobService.getBlobToStream('mycontainer', 'taskblob', fs.createWriteStream('output.txt'), function(error, result, response) {
+ if (!error) {
+ // blob retrieved
+ }
+});
+```
+
+To create a Shared Access Signature (SAS), use the **generateSharedAccessSignature** method. Additionally you can use the **date** helper functions to easily create a SAS that expires at some point relative to the current time.
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+
+var startDate = new Date();
+var expiryDate = new Date(startDate);
+expiryDate.setMinutes(startDate.getMinutes() + 100);
+startDate.setMinutes(startDate.getMinutes() - 100);
+
+var sharedAccessPolicy = {
+ AccessPolicy: {
+ Permissions: azure.BlobUtilities.SharedAccessPermissions.READ,
+ Start: startDate,
+ Expiry: expiryDate
+ }
+};
+
+var token = blobService.generateSharedAccessSignature(containerName, blobName, sharedAccessPolicy);
+var sasUrl = blobService.getUrl(containerName, blobName, token);
+```
+
+### Table Storage
+
+To ensure a table exists, call **createTableIfNotExists**:
+
+```Javascript
+var azure = require('azure-storage');
+var tableService = azure.createTableService();
+tableService.createTableIfNotExists('mytable', function(error, result, response) {
+ if (!error) {
+ // result contains true if created; false if already exists
+ }
+});
+```
+A new entity can be added by calling **insertEntity** or **insertOrReplaceEntity**:
+
+```Javascript
+var azure = require('azure-storage');
+var tableService = azure.createTableService();
+var entGen = azure.TableUtilities.entityGenerator;
+var entity = {
+ PartitionKey: entGen.String('part2'),
+ RowKey: entGen.String('row1'),
+ boolValueTrue: entGen.Boolean(true),
+ boolValueFalse: entGen.Boolean(false),
+ intValue: entGen.Int32(42),
+ dateValue: entGen.DateTime(new Date(Date.UTC(2011, 10, 25))),
+ complexDateValue: entGen.DateTime(new Date(Date.UTC(2013, 02, 16, 01, 46, 20)))
+};
+tableService.insertEntity('mytable', entity, function(error, result, response) {
+ if (!error) {
+ // result contains the ETag for the new entity
+ }
+});
+```
+
+
+Instead of creating entities manually, you can use **entityGenerator**:
+
+```Javascript
+var azure = require('azure-storage');
+var entGen = azure.TableUtilities.entityGenerator;
+var task = {
+ PartitionKey: entGen.String('hometasks'),
+ RowKey: entGen.String('1'),
+ description: entGen.String('take out the trash'),
+ dueDate: entGen.DateTime(new Date(Date.UTC(2015, 6, 20)))
+};
+```
+
+The method **retrieveEntity** can then be used to fetch the entity that was just inserted:
+
+```Javascript
+var azure = require('azure-storage');
+var tableService = azure.createTableService();
+tableService.retrieveEntity('mytable', 'part2', 'row1', function(error, result, response) {
+ if (!error) {
+ // result contains the entity
+ }
+});
+```
+
+The method **replaceEntity** or **insertOrReplaceEntity** can be called to update/edit an existing entry. In the following example we assume that an entity `'part2', 'row1'` with a field `'taskDone'` set to `false` already exists.
+
+```Javascript
+var azure = require('azure-storage');
+var tableService = azure.createTableService();
+var entity = {
+ PartitionKey: entGen.String('part2'),
+ RowKey: entGen.String('row1'),
+ taskDone: entGen.Boolean(true),
+};
+
+tableService.insertOrReplaceEntity('mytable', entity, function(error, result, response) {
+ if (!error) {
+ // result contains the entity with field 'taskDone' set to `true`
+ }
+});
+```
+
+Use **TableQuery** to build complex queries:
+
+```Javascript
+var azure = require('azure-storage');
+var tableService = azure.createTableService();
+var query = new azure.TableQuery()
+ .top(5)
+ .where('PartitionKey eq ?', 'part2');
+
+tableService.queryEntities('mytable', query, null, function(error, result, response) {
+ if (!error) {
+ // result.entries contains entities matching the query
+ }
+});
+```
+
+### Queue Storage
+
+The **createQueueIfNotExists** method can be used to ensure a queue exists:
+
+```Javascript
+var azure = require('azure-storage');
+var queueService = azure.createQueueService();
+queueService.createQueueIfNotExists('taskqueue', function(error) {
+ if (!error) {
+ // Queue exists
+ }
+});
+```
+
+The **createMessage** method can then be called to insert the message into the queue:
+
+```Javascript
+var queueService = azure.createQueueService();
+queueService.createMessage('taskqueue', 'Hello world!', function(error) {
+ if (!error) {
+ // Message inserted
+ }
+});
+```
+
+It is then possible to call the **getMessage** method, process the message and then call **deleteMessage** inside the callback. This two-step process ensures messages don't get lost when they are removed from the queue.
+
+```Javascript
+var queueService = azure.createQueueService(),
+ queueName = 'taskqueue';
+queueService.getMessages(queueName, function(error, serverMessages) {
+ if (!error) {
+ // Process the message in less than 30 seconds, the message
+ // text is available in serverMessages[0].messageText
+
+ queueService.deleteMessage(queueName, serverMessages[0].messageId, serverMessages[0].popReceipt, function(error) {
+ if (!error) {
+ // Message deleted
+ }
+ });
+ }
+});
+```
+
+### File Storage
+
+The **createShareIfNotExists** method can be used to create a
+share in which to store a file or a directory of files:
+
+```Javascript
+var azure = require('azure-storage');
+var fileService = azure.createFileService();
+fileService.createShareIfNotExists('taskshare', function(error, result, response) {
+ if (!error) {
+ // if result = true, share was created.
+ // if result = false, share already existed.
+ }
+});
+```
+
+To create a directory, the method **createDirectoryIfNotExists** can be used.
+
+```Javascript
+var azure = require('azure-storage');
+var fileService = azure.createFileService();
+
+fileService.createDirectoryIfNotExists('taskshare', 'taskdirectory', function(error, result, response) {
+ if (!error) {
+ // if result.created = true, share was created.
+ // if result.created = false, share already existed.
+ }
+});
+```
+
+To upload a file (assuming it is called task1-upload.txt and it is placed in the same folder as the script below), the method **createFileFromLocalFile** can be used.
+
+```Javascript
+var azure = require('azure-storage');
+var fileService = azure.createFileService();
+
+fileService.createFileFromLocalFile('taskshare', 'taskdirectory', 'taskfile', 'task1-upload.txt', function(error, result, response) {
+ if (!error) {
+ // file uploaded
+ }
+});
+```
+
+To upload a file from a stream, the method **createFileFromStream** can be used. The var `myFileBuffer` in the script below is a native Node Buffer, or ArrayBuffer object if within a browser environment.
+
+```Javascript
+ var stream = require('stream');
+ var azure = require('azure-storage');
+ var fileService = azure.createFileService();
+
+ var fileStream = new stream.Readable();
+ fileStream.push(myFileBuffer);
+ fileStream.push(null);
+
+ fileService.createFileFromStream('taskshare', 'taskdirectory', 'taskfile', fileStream, myFileBuffer.length, function(error, result, response) {
+ if (!error) {
+ // file uploaded
+ }
+ });
+```
+
+To create a file from a text string, the method **createFileFromText** can be used. A Node Buffer or ArrayBuffer object containing the text can also be supplied.
+
+```Javascript
+ var azure = require('azure-storage');
+ var fileService = azure.createFileService();
+
+ var text = 'Hello World!';
+
+ fileService.createFileFromText('taskshare', 'taskdirectory', 'taskfile', text, function(error, result, response) {
+ if (!error) {
+ // file created
+ }
+ });
+```
+
+There are also several ways to download files. For example, **getFileToStream** downloads the file to a stream:
+
+```Javascript
+var fileService = azure.createFileService();
+var fs = require('fs');
+fileService.getFileToStream('taskshare', 'taskdirectory', 'taskfile', fs.createWriteStream('output.txt'), function(error, result, response) {
+ if (!error) {
+ // file retrieved
+ }
+});
+```
+
+### Service Properties
+
+The **getServiceProperties** method can be used to fetch the logging, metrics and CORS settings on your storage account:
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+
+blobService.getServiceProperties(function(error, result, response) {
+ if (!error) {
+ var serviceProperties = result;
+ // properties are fetched
+ }
+});
+```
+
+The **setServiceProperties** method can be used to modify the logging, metrics and CORS settings on your storage account:
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+
+var serviceProperties = generateServiceProperties();
+
+blobService.setServiceProperties(serviceProperties, function(error, result, response) {
+ if (!error) {
+ // properties are set
+ }
+});
+
+function generateServiceProperties() {
+ return serviceProperties = {
+ Logging: {
+ Version: '1.0',
+ Delete: true,
+ Read: true,
+ Write: true,
+ RetentionPolicy: {
+ Enabled: true,
+ Days: 10,
+ },
+ },
+ HourMetrics: {
+ Version: '1.0',
+ Enabled: true,
+ IncludeAPIs: true,
+ RetentionPolicy: {
+ Enabled: true,
+ Days: 10,
+ },
+ },
+ MinuteMetrics: {
+ Version: '1.0',
+ Enabled: true,
+ IncludeAPIs: true,
+ RetentionPolicy: {
+ Enabled: true,
+ Days: 10,
+ },
+ },
+ Cors: {
+ CorsRule: [
+ {
+ AllowedOrigins: ['www.azure.com', 'www.microsoft.com'],
+ AllowedMethods: ['GET', 'PUT'],
+ AllowedHeaders: ['x-ms-meta-data*', 'x-ms-meta-target*', 'x-ms-meta-xyz', 'x-ms-meta-foo'],
+ ExposedHeaders: ['x-ms-meta-data*', 'x-ms-meta-source*', 'x-ms-meta-abc', 'x-ms-meta-bcd'],
+ MaxAgeInSeconds: 500,
+ },
+ {
+ AllowedOrigins: ['www.msdn.com', 'www.asp.com'],
+ AllowedMethods: ['GET', 'PUT'],
+ AllowedHeaders: ['x-ms-meta-data*', 'x-ms-meta-target*', 'x-ms-meta-xyz', 'x-ms-meta-foo'],
+ ExposedHeaders: ['x-ms-meta-data*', 'x-ms-meta-source*', 'x-ms-meta-abc', 'x-ms-meta-bcd'],
+ MaxAgeInSeconds: 500,
+ },
+ ],
+ },
+ };
+}
+```
+
+When modifying the service properties, you can fetch the properties and then modify the them to prevent overwriting the existing settings.
+
+```Javascript
+var azure = require('azure-storage');
+var blobService = azure.createBlobService();
+
+blobService.getServiceProperties(function(error, result, response) {
+ if (!error) {
+ var serviceProperties = result;
+
+ // modify the properties
+
+ blobService.setServiceProperties(serviceProperties, function(error, result, response) {
+ if (!error) {
+ // properties are set
+ }
+ });
+ }
+});
+```
+
+### Retry Policies
+
+By default, no retry will be performed with service instances newly created by Azure storage client library for Node.js.
+Two pre-written retry polices [ExponentialRetryPolicyFilter](http://azure.github.io/azure-storage-node/ExponentialRetryPolicyFilter.html) and [LinearRetryPolicyFilter](http://azure.github.io/azure-storage-node/LinearRetryPolicyFilter.html) are available with modifiable settings, and can be used through associating filter.
+Any custom retry logic may be used by customizing RetryPolicyFilter instance.
+
+For how to use pre-written retry policies and how to define customized retry policy, please refer to **retrypolicysample** in samples directory.
+
+## Code Samples
+
+How-Tos focused around accomplishing specific tasks are available on the [Microsoft Azure Node.js Developer Center](http://azure.microsoft.com/en-us/develop/nodejs/).
+
+* [How to use the Blob Service from Node.js](http://azure.microsoft.com/en-us/documentation/articles/storage-nodejs-how-to-use-blob-storage/)
+
+* [How to use the Table Service from Node.js](http://azure.microsoft.com/en-us/documentation/articles/storage-nodejs-how-to-use-table-storage/)
+
+* [How to use the Queue Service from Node.js](http://azure.microsoft.com/en-us/documentation/articles/storage-nodejs-how-to-use-queues/)
+
+# Running Tests
+
+Unit tests can then be run from the module's root directory using:
+
+```shell
+npm test
+```
+
+Running test is also supported by Grunt by:
+
+```shell
+grunt # mochaTest as the default task
+```
+
+By default the unit tests are ran with Nock recording data. To run tests against real storage account, please set environment variable to turn off Nock by:
+
+```
+set NOCK_OFF=true
+```
+
+and set up the following environment variable for storage account credentials by
+
+```Batchfile
+set AZURE_STORAGE_CONNECTION_STRING="valid storage connection string"
+```
+
+To record the data in a test pass against real storage account for future Nock usage:
+
+```Batchfile
+set AZURE_NOCK_RECORD=true
+```
+
+In order to be able to use a proxy like fiddler, an additional environment variable should be set up:
+
+```Batchfile
+set NODE_TLS_REJECT_UNAUTHORIZED=0
+set HTTP_PROXY=http://127.0.0.1:8888
+```
+
+On Linux, please use `export` other than `set` to set the variables.
+
+# Azure Storage JavaScript Client Library for Browsers
+
+Azure Storage Node.js Client Library is compatible with [Browserify](http://browserify.org/). This means you can bundle your Node.js application which depends on the Node.js Client Library using Browserify.
+
+You can also choose to download the JavaScript Client Library provided by us, or generate the library by yourself. Please refer to the [README.md](https://github.com/Azure/azure-storage-node/blob/master/browser/README.md) under `browser` folder for detailed usage guidelines.
+
+## Downloading Azure Storage JavaScript Client Library
+
+It's recommended to use the Azure Storage JavaScript Client Library provided by us. Please [download the latest library](https://aka.ms/downloadazurestoragejs).
+
+## Generating Azure Storage JavaScript Client Library
+
+We also provide browserify bundle scripts which generate Azure Storage JavaScript Client Library. The bundle script reduces the size of the Storage Client Library by splitting into smaller files, one per storage service. For more detailed information, refer to [README.md](https://github.com/Azure/azure-storage-node/blob/master/browser/README.md) under `browser` folder.
+
+# JsDoc
+
+JsDoc can be generated by `grunt jsdoc`.
+
+To load the docs by devserver after generation, run `grunt doc` and then browse the docs at [http://localhost:8888](http://localhost:8888).
+
+# Need Help?
+
+Be sure to check out the Microsoft Azure [Developer Forums on MSDN](http://go.microsoft.com/fwlink/?LinkId=234489) if you have trouble with the provided code or use StackOverflow.
+
+# Learn More
+
+- [Microsoft Azure Node.js Developer Center](http://azure.microsoft.com/en-us/develop/nodejs/)
+- [Azure Storage Team Blog](http://blogs.msdn.com/b/windowsazurestorage/)
+
+# Contribute
+
+We gladly accept community contributions.
+
+- Issues: Please report bugs using the Issues section of GitHub
+- Forums: Interact with the development teams on StackOverflow or the Microsoft Azure Forums
+- Source Code Contributions: If you would like to become an active contributor to this project please follow the instructions provided in [Contributing.md](CONTRIBUTING.md).
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
+
+For general suggestions about Microsoft Azure please use our [UserVoice forum](http://feedback.azure.com/forums/34192--general-feedback).
diff --git a/src/node_modules/azure-storage/browser/ChangeLog.md b/src/node_modules/azure-storage/browser/ChangeLog.md
new file mode 100644
index 0000000..252b00d
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/ChangeLog.md
@@ -0,0 +1,140 @@
+Note: This is the change log file for Azure Storage JavaScript Client Library.
+
+2019.04 Version 2.10.103
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.10.3.
+* Fixed callback not being called in _getBlobToLocalFile.
+* Removed retryInfo.retryable check in retrypolicyfilter.js.
+* Removed comment about maxResults.
+* Fixed Travis-CI failed validation.
+* Updated latest links and descriptions to V10 SDK in readme.md.
+
+2018.10 Version 2.10.102
+
+ALL
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.10.2.
+* Optimized browser samples and other documents.
+* Added JSv10 link and docs.microsoft.com link.
+
+FILE
+* Fixed an issue that empty text isn’t supported in `createFileFromText`.
+
+2018.08 Version 2.10.101
+
+ALL
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.10.1.
+* Fixed a bug that content type value is incorrect for json.
+* Fixed an issue that user agent is set in browser environment.
+
+2018.06 Version 2.10.100
+
+ALL
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.10.0.
+* Updated storage service version to 2018-03-28.
+
+BLOB
+* Fixed a bug that `DeleteRetentionPolicy.Days` should be `number` instead of `string` when calling `getServiceProperties`.
+* Added a method `getAccountProperties` to `blobService`.
+* Added a method `createBlockFromURL` to `blobService`.
+* Added support for static website service properties (in preview).
+
+2018.05 Version 2.9.100-preview
+
+ALL
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.9.0-preview.
+* Updated storage service version to 2017-11-09.
+* Added `/* eslint-disable */` to generated JS files to avoid eslint warnings when using with create-react-app.
+* Added `progress` event for `SpeedSummary` class, which will be triggered when every progress updates.
+
+BLOB
+* Added `createBlobServiceWithTokenCredential()` to create `BlobService` object with bearer tokens such as OAuth access token (in preview).
+* Added support for '$web' as a valid blob container name for static website.
+* Added support for write-once read-many containers (in preview).
+* The `Get Container Properties` and `List Containers` APIs now return two new properties indicating whether the container has an immutability policy or a legal hold.
+* The `Get Blob Properties` and `List Blobs` APIs now return the creation time of the blob as a property.
+
+QUEUE
+* Added `createQueueServiceWithTokenCredential()` to create `QueueService` object with bearer tokens such as OAuth access token (in preview).
+
+2018.04 Version 2.8.100
+
+* Fixed a bug that retry policy will not retry for XHR error in browsers.
+* Updated README.md under browser folder to make it more clear about the zip file downloading link.
+* Updated github.io API reference title to include JavaScript.
+* Updated local HTTP server requirements for IE11 and Chrome 56 in samples and documents.
+* Added support for running UT/FT in browsers like Chrome based on Karma, with command `npm run jstest`.
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.8.2.
+
+2018.03 Version 0.2.8-preview.15
+
+* Supported UMD module standard.
+* Dropped `azure-storage.common.js`.
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.8.1.
+
+2018.02 Version 0.2.8-preview.14
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.8.0.
+
+2017.12 Version 0.2.7-preview.13
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.7.0.
+
+2017.10 Version 0.2.6-preview.12
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.6.0.
+
+2017.09 Version 0.2.5-preview.11
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.5.0.
+
+2017.08 Version 0.2.4-preview.10
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.4.0.
+
+2017.08 Version 0.2.3-preview.9
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.3.0.
+
+2017.08 Version 0.2.2-preview.8
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.2.2.
+
+2017.07 Version 0.2.2-preview.7
+
+* Added browser specific APIs for blobs and files uploading.
+ * `BlobService.createBlockBlobFromBrowserFile`
+ * `BlobService.createPageBlobFromBrowserFile`
+ * `BlobService.createAppendBlobFromBrowserFile`
+ * `BlobService.appendFromBrowserFile`
+ * `FileService.createFileFromBrowserFile`
+* Updated samples with above new added APIs.
+* Dropped dependency to browserify-fs.
+
+2017.07 Version 0.2.2-preview.6
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.2.1.
+
+2017.06 Version 0.2.2-preview.5
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.2.0.
+
+2017.05 Version 0.2.1-preview.4
+
+* Reduced footprint of the generated JavaScript files.
+* Removed 7 local-file related APIs which are limited by browser's sandbox.
+
+2017.03 Version 0.2.1-preview.3
+
+* Fixed missing 100% upload progress issue in blob sample for uploading blobs smaller than 32MB.
+* Added speedSummary code example in the blob & file samples.
+
+2017.03 Version 0.2.1-preview.2
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.1.0.
+
+2017.03 Version 0.2.0-preview.1
+
+* Generated browser compatible JavaScript files based on Microsoft Azure Storage SDK for Node.js 2.0.0.
+* Added bundle scripts to generate Azure Storage JavaScript Client Library.
+* Added npm command `npm run genjs` to generate JavaScript Client Library.
+* Added samples for Azure Storage JavaScript Client Library.
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/README.md b/src/node_modules/azure-storage/browser/README.md
new file mode 100644
index 0000000..f6bc1c8
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/README.md
@@ -0,0 +1,109 @@
+# Azure Storage JavaScript Client Library for Browsers
+
+## Downloading
+
+It's recommended to use the Azure Storage JavaScript Client Library provided by us. Please [download the latest library](https://aka.ms/downloadazurestoragejs).
+
+There are 8 generated JavaScript files for Azure Storage JavaScript Client Library:
+- `azure-storage.blob.js` and `azure-storage.blob.min.js` contain the Azure Storage blob service operation logic
+- `azure-storage.table.js` and `azure-storage.table.min.js` contain the Azure Storage table service operation logic
+- `azure-storage.queue.js` and `azure-storage.queue.min.js` contain the Azure Storage queue service operation logic
+- `azure-storage.file.js` and `azure-storage.file.min.js` contain the Azure Storage file service operation logic
+
+We also provide samples to guide you quickly start with the Azure Storage JavaScript Client Library. In the [JavaScript Client Library zip file](https://aka.ms/downloadazurestoragejs) or following online links, you will find 4 HTML samples:
+- [sample-blob.html](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-blob.html) demonstrates how to operate with Azure Storage blob service in the browser
+- [sample-table.html](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-table.html) demonstrates how to operate with Azure Storage table service in the browser
+- [sample-queue.html](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-queue.html) demonstrates how to operate with Azure Storage queue service in the browser
+- [sample-file.html](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-file.html) demonstrates how to operate with Azure Storage file service in the browser
+
+After generating the JavaScript Client Library, you can try the samples in browsers such as Chrome/Edge/Firefox directly.
+
+**Note**: An HTTP server should be set to host the samples for IE11 and Chrome (56 or newer versions).
+
+Or you can directly try with following online samples:
+- [sample-blob](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-blob.html)
+- [sample-table](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-table.html)
+- [sample-queue](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-queue.html)
+- [sample-file](https://dmrelease.blob.core.windows.net/azurestoragejssample/samples/sample-file.html)
+
+## Module Support
+
+Above JavaScript files are all [UMD compatible](https://github.com/umdjs/umd). You can load them in a CommonJS or AMD environment by JavaScript module loaders. If no module system is found, following global variables will be set:
+- `AzureStorage.Blob`
+- `AzureStorage.Table`
+- `AzureStorage.Queue`
+- `AzureStorage.File`
+
+## Compatibility
+
+Compatibility with mobile browsers have not been fully validated, please open issues when you get errors.
+
+# Running Tests against Browsers
+
+Running tests against Chrome by default. The Storage Account should be configured with CORS support before running test. Please see above online samples about how to configure CORS rules for an account.
+
+```
+set AZURE_STORAGE_CONNECTION_STRING="valid storage connection string"
+npm install
+npm run jstest
+```
+
+## Generating a Custom Azure Storage JavaScript Client Library
+
+If you wish to customize the library and generate the Azure Storage JavaScript Client Library, you can follow the following steps.
+
+We provide browserify bundle scripts which generate Azure Storage JavaScript Client Library. The bundle script reduces the size of the Storage Client Library by splitting into smaller files, one per storage service.
+
+The generated JavaScript Client Library includes 8 separated JavaScript files:
+- `azure-storage.blob.js`
+- `azure-storage.table.js`
+- `azure-storage.queue.js`
+- `azure-storage.file.js`
+- `azure-storage.blob.min.js`
+- `azure-storage.table.min.js`
+- `azure-storage.queue.min.js`
+- `azure-storage.file.min.js`
+
+Let's get started to generate the Azure Storage JavaScript Client Library!
+
+### Step 1: Cloning Repo
+
+Azure Storage JavaScript Client Library is generated from Azure Storage SDK for Node.js. Clone `azure-storage-node` repo with following command:
+
+```Batchfile
+git clone https://github.com/Azure/azure-storage-node.git
+```
+
+### Step 2: Installing Node.js Modules
+
+Change to the root directory of the cloned repo:
+
+```Batchfile
+cd azure-storage-node
+```
+
+Install the dependent Node.js modules:
+
+```Batchfile
+npm install
+```
+
+### Step 3: Generating JavaScript Client Library with Bundle Scripts
+
+We provide bundle scripts to help quickly generate the JavaScript Client Library. At the root directory of the cloned repo:
+
+```Batchfile
+npm run genjs [VERSION_NUMBER]
+```
+
+### Step 4: Finding the Generated JavaScript Files
+
+If everything goes well, the generated JavaScript files should be saved to `azure-storage-node/browser/bundle`. There will be 8 generated JavaScript files totally:
+- `azure-storage.blob.js`
+- `azure-storage.table.js`
+- `azure-storage.queue.js`
+- `azure-storage.file.js`
+- `azure-storage.blob.min.js`
+- `azure-storage.table.min.js`
+- `azure-storage.queue.min.js`
+- `azure-storage.file.min.js`
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/azure-storage.blob.export.js b/src/node_modules/azure-storage/browser/azure-storage.blob.export.js
new file mode 100644
index 0000000..3bd7a28
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/azure-storage.blob.export.js
@@ -0,0 +1,74 @@
+//
+// Copyright (c) Microsoft and contributors. All rights reserved.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+//
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+module.exports.generateDevelopmentStorageCredentials = function (proxyUri) {
+ var devStore = 'UseDevelopmentStorage=true;';
+ if(proxyUri){
+ devStore += 'DevelopmentStorageProxyUri=' + proxyUri;
+ }
+
+ return devStore;
+};
+
+var BlobService = require('../lib/services/blob/blobservice.browser');
+
+module.exports.BlobService = BlobService;
+module.exports.BlobUtilities = require('../lib/services/blob/blobutilities');
+
+module.exports.createBlobService = function (storageAccountOrConnectionString, storageAccessKey, host) {
+ return new BlobService(storageAccountOrConnectionString, storageAccessKey, host, null);
+};
+
+module.exports.createBlobServiceWithSas = function (host, sasToken) {
+ return new BlobService(null, null, host, sasToken);
+};
+
+module.exports.createBlobServiceWithTokenCredential = function (host, tokenCredential) {
+ return new BlobService(null, null, host, null, null, tokenCredential);
+};
+
+module.exports.createBlobServiceAnonymous = function (host) {
+ return new BlobService(null, null, host, null);
+};
+
+var azureCommon = require('../lib/common/common.browser');
+var StorageServiceClient = azureCommon.StorageServiceClient;
+var SharedKey = azureCommon.SharedKey;
+
+module.exports.generateAccountSharedAccessSignature = function(storageAccountOrConnectionString, storageAccessKey, sharedAccessAccountPolicy)
+{
+ var storageSettings = StorageServiceClient.getStorageSettings(storageAccountOrConnectionString, storageAccessKey);
+ var sharedKey = new SharedKey(storageSettings._name, storageSettings._key);
+
+ return sharedKey.generateAccountSignedQueryString(sharedAccessAccountPolicy);
+};
+
+module.exports.Constants = azureCommon.Constants;
+module.exports.StorageUtilities = azureCommon.StorageUtilities;
+module.exports.AccessCondition = azureCommon.AccessCondition;
+
+module.exports.SR = azureCommon.SR;
+module.exports.StorageServiceClient = StorageServiceClient;
+module.exports.Logger = azureCommon.Logger;
+module.exports.WebResource = azureCommon.WebResource;
+module.exports.Validate = azureCommon.validate;
+module.exports.date = azureCommon.date;
+module.exports.TokenCredential = azureCommon.TokenCredential;
+
+// Other filters
+module.exports.LinearRetryPolicyFilter = azureCommon.LinearRetryPolicyFilter;
+module.exports.ExponentialRetryPolicyFilter = azureCommon.ExponentialRetryPolicyFilter;
+module.exports.RetryPolicyFilter = azureCommon.RetryPolicyFilter;
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/azure-storage.file.export.js b/src/node_modules/azure-storage/browser/azure-storage.file.export.js
new file mode 100644
index 0000000..61e7226
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/azure-storage.file.export.js
@@ -0,0 +1,65 @@
+//
+// Copyright (c) Microsoft and contributors. All rights reserved.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+//
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+module.exports.generateDevelopmentStorageCredentials = function (proxyUri) {
+ var devStore = 'UseDevelopmentStorage=true;';
+ if(proxyUri){
+ devStore += 'DevelopmentStorageProxyUri=' + proxyUri;
+ }
+
+ return devStore;
+};
+
+var FileService = require('../lib/services/file/fileservice.browser');
+
+module.exports.FileService = FileService;
+module.exports.FileUtilities = require('../lib/services/file/fileutilities');
+
+module.exports.createFileService = function (storageAccountOrConnectionString, storageAccessKey, host) {
+ return new FileService(storageAccountOrConnectionString, storageAccessKey, host);
+};
+
+module.exports.createFileServiceWithSas = function (hostUri, sasToken) {
+ return new FileService(null, null, hostUri, sasToken);
+};
+
+var azureCommon = require('../lib/common/common.browser');
+var StorageServiceClient = azureCommon.StorageServiceClient;
+var SharedKey = azureCommon.SharedKey;
+
+module.exports.generateAccountSharedAccessSignature = function(storageAccountOrConnectionString, storageAccessKey, sharedAccessAccountPolicy)
+{
+ var storageSettings = StorageServiceClient.getStorageSettings(storageAccountOrConnectionString, storageAccessKey);
+ var sharedKey = new SharedKey(storageSettings._name, storageSettings._key);
+
+ return sharedKey.generateAccountSignedQueryString(sharedAccessAccountPolicy);
+};
+
+module.exports.Constants = azureCommon.Constants;
+module.exports.StorageUtilities = azureCommon.StorageUtilities;
+module.exports.AccessCondition = azureCommon.AccessCondition;
+
+module.exports.SR = azureCommon.SR;
+module.exports.StorageServiceClient = StorageServiceClient;
+module.exports.Logger = azureCommon.Logger;
+module.exports.WebResource = azureCommon.WebResource;
+module.exports.Validate = azureCommon.validate;
+module.exports.date = azureCommon.date;
+
+// Other filters
+module.exports.LinearRetryPolicyFilter = azureCommon.LinearRetryPolicyFilter;
+module.exports.ExponentialRetryPolicyFilter = azureCommon.ExponentialRetryPolicyFilter;
+module.exports.RetryPolicyFilter = azureCommon.RetryPolicyFilter;
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/azure-storage.queue.export.js b/src/node_modules/azure-storage/browser/azure-storage.queue.export.js
new file mode 100644
index 0000000..45726ee
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/azure-storage.queue.export.js
@@ -0,0 +1,71 @@
+//
+// Copyright (c) Microsoft and contributors. All rights reserved.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+//
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+module.exports.generateDevelopmentStorageCredentials = function (proxyUri) {
+ var devStore = 'UseDevelopmentStorage=true;';
+ if(proxyUri){
+ devStore += 'DevelopmentStorageProxyUri=' + proxyUri;
+ }
+
+ return devStore;
+};
+
+var QueueService = require('../lib/services/queue/queueservice');
+
+module.exports.QueueService = QueueService;
+module.exports.QueueUtilities = require('../lib/services/queue/queueutilities');
+module.exports.QueueMessageEncoder = require('../lib/services/queue/queuemessageencoder');
+
+module.exports.createQueueService = function (storageAccountOrConnectionString, storageAccessKey, host) {
+ return new QueueService(storageAccountOrConnectionString, storageAccessKey, host);
+};
+
+module.exports.createQueueServiceWithSas = function(hostUri, sasToken) {
+ return new QueueService(null, null, hostUri, sasToken);
+};
+
+module.exports.createQueueServiceWithTokenCredential = function (host, tokenCredential) {
+ return new QueueService(null, null, host, null, null, tokenCredential);
+};
+
+var azureCommon = require('../lib/common/common.browser');
+var StorageServiceClient = azureCommon.StorageServiceClient;
+var SharedKey = azureCommon.SharedKey;
+
+module.exports.generateAccountSharedAccessSignature = function(storageAccountOrConnectionString, storageAccessKey, sharedAccessAccountPolicy)
+{
+ var storageSettings = StorageServiceClient.getStorageSettings(storageAccountOrConnectionString, storageAccessKey);
+ var sharedKey = new SharedKey(storageSettings._name, storageSettings._key);
+
+ return sharedKey.generateAccountSignedQueryString(sharedAccessAccountPolicy);
+};
+
+module.exports.Constants = azureCommon.Constants;
+module.exports.StorageUtilities = azureCommon.StorageUtilities;
+module.exports.AccessCondition = azureCommon.AccessCondition;
+
+module.exports.SR = azureCommon.SR;
+module.exports.StorageServiceClient = StorageServiceClient;
+module.exports.Logger = azureCommon.Logger;
+module.exports.WebResource = azureCommon.WebResource;
+module.exports.Validate = azureCommon.validate;
+module.exports.date = azureCommon.date;
+module.exports.TokenCredential = azureCommon.TokenCredential;
+
+// Other filters
+module.exports.LinearRetryPolicyFilter = azureCommon.LinearRetryPolicyFilter;
+module.exports.ExponentialRetryPolicyFilter = azureCommon.ExponentialRetryPolicyFilter;
+module.exports.RetryPolicyFilter = azureCommon.RetryPolicyFilter;
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/azure-storage.table.export.js b/src/node_modules/azure-storage/browser/azure-storage.table.export.js
new file mode 100644
index 0000000..9a93dd2
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/azure-storage.table.export.js
@@ -0,0 +1,66 @@
+//
+// Copyright (c) Microsoft and contributors. All rights reserved.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+//
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+module.exports.generateDevelopmentStorageCredentials = function (proxyUri) {
+ var devStore = 'UseDevelopmentStorage=true;';
+ if(proxyUri){
+ devStore += 'DevelopmentStorageProxyUri=' + proxyUri;
+ }
+
+ return devStore;
+};
+
+var TableService = require('../lib/services/table/tableservice');
+module.exports.TableService = TableService;
+module.exports.TableQuery = require('../lib/services/table/tablequery');
+module.exports.TableBatch = require('../lib/services/table/tablebatch');
+module.exports.TableUtilities = require('../lib/services/table/tableutilities');
+
+module.exports.createTableService = function (storageAccountOrConnectionString, storageAccessKey, host) {
+ return new TableService(storageAccountOrConnectionString, storageAccessKey, host);
+};
+
+module.exports.createTableServiceWithSas = function (hostUri, sasToken) {
+ return new TableService(null, null, hostUri, sasToken);
+};
+
+var azureCommon = require('../lib/common/common.browser');
+var StorageServiceClient = azureCommon.StorageServiceClient;
+var SharedKey = azureCommon.SharedKey;
+
+module.exports.generateAccountSharedAccessSignature = function(storageAccountOrConnectionString, storageAccessKey, sharedAccessAccountPolicy)
+{
+ var storageSettings = StorageServiceClient.getStorageSettings(storageAccountOrConnectionString, storageAccessKey);
+ var sharedKey = new SharedKey(storageSettings._name, storageSettings._key);
+
+ return sharedKey.generateAccountSignedQueryString(sharedAccessAccountPolicy);
+};
+
+module.exports.Constants = azureCommon.Constants;
+module.exports.StorageUtilities = azureCommon.StorageUtilities;
+module.exports.AccessCondition = azureCommon.AccessCondition;
+
+module.exports.SR = azureCommon.SR;
+module.exports.StorageServiceClient = StorageServiceClient;
+module.exports.Logger = azureCommon.Logger;
+module.exports.WebResource = azureCommon.WebResource;
+module.exports.Validate = azureCommon.validate;
+module.exports.date = azureCommon.date;
+
+// Other filters
+module.exports.LinearRetryPolicyFilter = azureCommon.LinearRetryPolicyFilter;
+module.exports.ExponentialRetryPolicyFilter = azureCommon.ExponentialRetryPolicyFilter;
+module.exports.RetryPolicyFilter = azureCommon.RetryPolicyFilter;
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/bundle.js b/src/node_modules/azure-storage/browser/bundle.js
new file mode 100644
index 0000000..4572ca7
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/bundle.js
@@ -0,0 +1,77 @@
+//
+// Copyright (c) Microsoft and contributors. All rights reserved.
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+//
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+var browserify = require('browserify');
+var fs = require('fs');
+var path = require('path');
+var UglifyJS = require('uglify-js');
+
+var version = process.argv[2] || process.env.AZURE_STORAGE_JAVASCRIPT_VERSION || '';
+var license = [
+ '// Azure Storage JavaScript Client Library ' + version,
+ '// Copyright (c) Microsoft and contributors. All rights reserved.',
+ '/* eslint-disable */'
+].join('\n') + '\n';
+
+var outputFolder = 'bundle';
+var outputFolderPath = path.resolve(__dirname, outputFolder);
+
+console.log('Generating Azure Storage JavaScript Client Library to ' + outputFolderPath + ' ...');
+
+if (version === '') {
+ console.warn(
+ 'No version number provided.',
+ 'You can set up a version number by first parameter of bundle.js or environment value AZURE_STORAGE_JAVASCRIPT_VERSION'
+ );
+}
+
+if (!fs.existsSync(outputFolderPath)) {
+ fs.mkdirSync(outputFolderPath);
+}
+
+function build(exportFilePath, outputFilePath, moduleName, isMinify) {
+ browserify(exportFilePath, {standalone: moduleName}).bundle(function (err, src) {
+ if (err) {
+ console.error('Failed when parsing', exportFilePath, err);
+ return;
+ }
+
+ var code = (src || '').toString();
+ if (isMinify) {
+ result = UglifyJS.minify(code.trim());
+ if (result.error) {
+ console.error('Minify failed when parsing', exportFilePath, err);
+ return;
+ }
+
+ code = result.code;
+ }
+
+ var ws = fs.createWriteStream(outputFilePath);
+ ws.write(license);
+ ws.write(code);
+ ws.end();
+ });
+}
+
+build(path.resolve(__dirname, 'azure-storage.blob.export.js'), path.resolve(outputFolderPath, 'azure-storage.blob.js'), 'AzureStorage.Blob');
+build(path.resolve(__dirname, 'azure-storage.table.export.js'), path.resolve(outputFolderPath, 'azure-storage.table.js'), 'AzureStorage.Table');
+build(path.resolve(__dirname, 'azure-storage.queue.export.js'), path.resolve(outputFolderPath, 'azure-storage.queue.js'), 'AzureStorage.Queue');
+build(path.resolve(__dirname, 'azure-storage.file.export.js'), path.resolve(outputFolderPath, 'azure-storage.file.js'), 'AzureStorage.File');
+build(path.resolve(__dirname, 'azure-storage.blob.export.js'), path.resolve(outputFolderPath, 'azure-storage.blob.min.js'), 'AzureStorage.Blob', true);
+build(path.resolve(__dirname, 'azure-storage.table.export.js'), path.resolve(outputFolderPath, 'azure-storage.table.min.js'), 'AzureStorage.Table', true);
+build(path.resolve(__dirname, 'azure-storage.queue.export.js'), path.resolve(outputFolderPath, 'azure-storage.queue.min.js'), 'AzureStorage.Queue', true);
+build(path.resolve(__dirname, 'azure-storage.file.export.js'), path.resolve(outputFolderPath, 'azure-storage.file.min.js'), 'AzureStorage.File', true);
\ No newline at end of file
diff --git a/src/node_modules/azure-storage/browser/samples/cors.PNG b/src/node_modules/azure-storage/browser/samples/cors.PNG
new file mode 100644
index 0000000..4f6a97f
Binary files /dev/null and b/src/node_modules/azure-storage/browser/samples/cors.PNG differ
diff --git a/src/node_modules/azure-storage/browser/samples/sample-blob.html b/src/node_modules/azure-storage/browser/samples/sample-blob.html
new file mode 100644
index 0000000..43364e4
--- /dev/null
+++ b/src/node_modules/azure-storage/browser/samples/sample-blob.html
@@ -0,0 +1,498 @@
+
+
+
+
+
+ Azure Storage JavaScript Client Library Sample for Blob Operations
+
+
+
+
+
+
Azure Storage JavaScript Client Library Sample for Blob Operations
+
+
In this sample, we will demonstrate common scenarios for Azure Blob Storage that includes creating, listing and deleting containers and blobs.
+
+
Azure Blob storage is a service for storing large amounts of unstructured object data, such as text or binary data, that can be accessed from anywhere in the world via HTTP or HTTPS. You can use Blob storage to expose data publicly to the world, or to store application data privately.
+
+
+
+ Note: You may need set up a HTTP server to host this sample for IE11 and latest Chrome.
+
+
+
+
Contents:
+
+
+
Step 1: Preparing an Azure Storage account with CORS rules set
+
Cross-origin resource sharing, or CORS, must be configured on the Azure Storage account to be accessed directly from JavaScript in the browser.
+ You are able to set the CORS rules for specific Azure Storage account on the Azure Portal.
+ The "Allowed origins" could be set to "*" to allow all the origins in this sample.
+ For more information about CORS, see Cross-Origin Resource Sharing (CORS).
+
+
+
Step 2: Importing Azure Storage JavaScript Client Library
+
+ Importing azure-storage.blob.js in your HTML file for blob operations.
+
+
+<script src="azure-storage.blob.js"></script>
+
+
+
Step 3: Creating an Azure Storage Blob Service Object
+
+ The BlobService object lets you work with containers and blobs.
+ Following code creates a BlobService object with storage account and SAS Token.
+
+
+var blobUri = 'https://' + 'STORAGE_ACCOUNT' + '.blob.core.windows.net';
+var blobService = AzureStorage.Blob.createBlobServiceWithSas(blobUri, 'SAS_TOKEN');
+
+
+ You can load Azure Storage JavaScript Client Library in a CommonJS or AMD environment by JavaScript module loaders. If no module system is found, global variable AzureStorage.Blob will be set, which is the start point where we can create service objects for blob and access to the storage utilities.
+
+
+
+
How to get full detailed API definitions? Currently, the JavaScript Client Library shares almost the same API definitions with Node.js SDK, besides Node.js runtime specific APIs.
+ Please check API details on
Azure Storage API reference documents. The JavaScript global variable
AzureStorage.Blob is just like the object
require('azure-storage') returns in Node.js, but limits to Blob related interfaces.
+ Go to
BlobService to view possible methods provided by
BlobService class.
+
+
+
+
+
Warning: Azure Storage JavaScript Client Library also supports creating
BlobService based on Storage Account Key for authentication besides SAS Token.
+ However, for security concerns, we recommend use of a limited time SAS Token, generated by a backend web server using a
Stored Access Policy.
+
+
+
+
Step 4: Container Operations
+
+ A container provides a grouping of blobs. All blobs must be in a container. An account can contain an unlimited number of containers. A container can store an unlimited number of blobs. Note that the container name must be lowercase.
+ BlobService object provides plenty of interfaces for container operations.
+
+
+
List Containers
+
BlobService provides listContainersSegmented and listContainersSegmentedWithPrefix for retrieving the containers list under a storage account.
+
+blobService.listContainersSegmented(null, function (error, results) {
+ if (error) {
+ // List container error
+ } else {
+ for (var i = 0, container; container = results.entries[i]; i++) {
+ // Deal with container object
+ }
+ }
+});
+
+
+
Create Container
+
BlobService provides createContainer and createContainerIfNotExists for creating a container under a storage account.
+
+blobService.createContainerIfNotExists('mycontainer', function(error, result) {
+ if (error) {
+ // Create container error
+ } else {
+ // Create container successfully
+ }
+});
+
+
+
Delete Container
+
BlobService provides deleteContainer and deleteContainerIfExists for deleting a container under a storage account.
+
+blobService.deleteContainerIfExists('mycontainer', function(error, result) {
+ if (error) {
+ // Delete container error
+ } else {
+ // Delete container successfully
+ }
+});
+
+
+
Executable Example
+
+ The sample will try to create an Azure Storage blob service object based on SAS Token authorization.
+ Enter your Azure Storage account name and SAS Token here, and executable examples in following steps dependent on the settings here.
+ Make sure you have set the CORS rules for the Azure Storage blob service, and the SAS Token is in valid period.
+
+
+
+
+
+
In the following executable example, you can try to list all the containers under your storage account settings, and try to create or delete one container from your account.
+
+ Click button to view the container list under your Azure Storage account
-
+
Click button to create a container under your Azure Storage account:
+
+
+ Click "Delete" button in the container list to delete the container under your Azure Storage account
Click "Select" button to select and operate with the blobs in next step
+
+
+
Step 5: Blob Operations
+
Blob: A file of any type and size. Azure Storage offers three types of blobs: block blobs, page blobs, and append blobs.
+
Block blobs are ideal for storing text or binary files, such as documents and media files. Append blobs are similar to block blobs in that they are made up of blocks, but they are optimized for append operations, so they are useful for logging scenarios. A single block blob can contain up to 50,000 blocks of up to 100 MB each, for a total size of slightly more than 4.75 TB (100 MB X 50,000). A single append blob can contain up to 50,000 blocks of up to 4 MB each, for a total size of slightly more than 195 GB (4 MB X 50,000).
+
Page blobs can be up to 1 TB in size, and are more efficient for frequent read/write operations. Azure Virtual Machines use page blobs as OS and data disks.
+
For details about naming containers and blobs, see Naming and Referencing Containers, Blobs, and Metadata.
+
+
List Blobs
+
BlobService provides listBlobsSegmented and listBlobsSegmentedWithPrefix for retrieving the blobs list under a container.
+
+blobService.listBlobsSegmented('mycontainer', null, function (error, results) {
+ if (error) {
+ // List blobs error
+ } else {
+ for (var i = 0, blob; blob = results.entries[i]; i++) {
+ // Deal with blob object
+ }
+ }
+});
+
+
Upload Blob
+
BlobService provides createBlockBlobFromBrowserFile, createPageBlobFromBrowserFile, createAppendBlobFromBrowserFile and appendFromBrowserFile for uploading or appending a blob from an HTML file in browsers.
+
+
+
Uploading blob from stream. You can set up the blob name as well as the size of this uploading session.
+
+// If one file has been selected in the HTML file input element
+var file = document.getElementById('fileinput').files[0];
+
+var customBlockSize = file.size > 1024 * 1024 * 32 ? 1024 * 1024 * 4 : 1024 * 512;
+blobService.singleBlobPutThresholdInBytes = customBlockSize;
+
+var finishedOrError = false;
+var speedSummary = blobService.createBlockBlobFromBrowserFile('mycontainer', file.name, file, {blockSize : customBlockSize}, function(error, result, response) {
+ finishedOrError = true;
+ if (error) {
+ // Upload blob failed
+ } else {
+ // Upload successfully
+ }
+});
+refreshProgress();
+
+
Checking the upload progress with speedSummary object.
+
+speedSummary.on('progress', function () {
+ var process = speedSummary.getCompletePercent();
+ displayProcess(process);
+});
+
+
+
+
Warning:
+ By default, the
speedSummary.getCompletePercent() only updates progress when a block is uploaded to server. There are 2 default settings that may influence the upload progress display.
+
+
+ blobService.singleBlobPutThresholdInBytes is the maximum size (default 32MB), in bytes, of a blob before it must be separated into blocks.- Option
{blockSize: SizeInBytes} of blobService.createBlockBlobFromStream() is the size (default 4MB) of every block in the storage layer.
+
+
+ This means, by default, blobs smaller than 32MB will only get the progress update when the upload is over, and blobs larger than 32MB will update the process every 4MB.
+ For slow connections or progress reporting for small blobs, you can customize both the two settings into samller values such as 1MB or 512KB. Thus the progress will update with the smaller step you set.
+ However, very small block sizes will impact the storage performance especially for a large blob.
+
+
+
+
Download Blob
+
+ BlobService provides interfaces for downloading a blob into browser memory.
+ Because of browser's sandbox limitation, we cannot save the downloaded data trunks into disk until we get all the data trunks of a blob into browser memory.
+ The browser's memory size is also limited especially for downloading huge blobs, so it's recommended to download a blob in browser with SAS Token authorized link directly.
+
+
+ Shared access signatures (SAS) are a secure way to provide granular access to blobs and containers without providing your storage account name or keys. Shared access signatures are often used to provide limited access to your data, such as allowing a mobile app to access blobs.
+ The following code example generates a new shared access policy that allows the shared access signatures holder to perform read operations on the myblob blob, and expires 100 minutes after the time it is created.
+
+
+
+ Note: You can choose to use the SAS Token in browser side, or generate a temporary SAS Token dynamically in your server side with Azure Storage C# or Node.js SDKs etc. according to your security requirements.
+
+
+
+var downloadLink = blobService.getUrl('mycontainer', 'myblob', 'SAS_TOKEN');
+
+
+
Delete Blob
+
BlobService provides deleteContainer and deleteContainerIfExists for deleting a blob under a storage account.
+
+blobService.deleteBlobIfExists(container, blob, function(error, result) {
+ if (error) {
+ // Delete blob failed
+ } else {
+ // Delete blob successfully
+ }
+});
+
+
Executable Example
+
After clicked the "Select" button on the container list in last step, you are able to operate with the blobs under the selected container.
+
+
+
+ Click button to view the blobs under your selected container
+ Click button to upload a local file to current container after selecting a file:
+
+
Click "Delete" button to delete the blob
Click "Download" link to download a blob to local
+
+
+
Uploaded Bytes:
+
+
+
+
+
Step 6: Creating your JavaScript Application based on Azure Storage JavaScript Client Library
+
+ - Setting CORS rules for your selected Azure-Storage account blob service.
+ - Including functional file(s) needed, such as "azure-storage.blob.js" for blob operation.
+ - Using keyword "AzureStorage.Blob" to access to Azure storage JavaScript APIs for blobs.
+ - Referring to API documents for detailed API definitions.
+
+
You can view the source code of this sample for detailed reference.
+
+
+
Azure Storage JavaScript Client Library Sample for File Operations
+
+
In this sample, we will demonstrate common scenarios for Azure File Storage that includes creating, listing and deleting file shares, directories and files.
+
+
Azure File storage is a service for storing large amounts of unstructured object data, such as text or binary data, that can be accessed from anywhere in the world via HTTP or HTTPS. You can use file storage to expose data publicly to the world, or to store application data privately.
+
With Azure File storage, you can migrate legacy applications that rely on file shares to Azure quickly and without costly rewrites. Applications running in Azure virtual machines or cloud services or from on-premises clients can mount a file share in the cloud, just as a desktop application mounts a typical SMB share. Any number of application components can then mount and access the File storage share simultaneously. In this sample, you are able to create a file service with storage account and SAS Token. Based on the file service, you could create a file share, list files, upload files and delete files.
+
+
+
+ Note: You may need set up a HTTP server to host this sample for IE11 and latest Chrome.
+
+
+
+
Contents:
+
+
+
Step 1: Preparing an Azure Storage account with CORS rules set
+
Cross-origin resource sharing, or CORS, must be configured on the Azure Storage account to be accessed directly from JavaScript in the browser.
+ You are able to set the CORS rules for specific Azure Storage account on the Azure Portal.
+ The "Allowed origins" could be set to "*" to allow all the origins in this sample.
+ For more information about CORS, see Cross-Origin Resource Sharing (CORS).
+
+
+
Step 2: Importing Azure Storage JavaScript Files
+
+ Importing azure-storage.file.js in your HTML file for file operations.
+
+
+<script src="azure-storage.file.js"></script>
+
+
+
Step 3: Creating an Azure Storage File Service Object
+
+ The FileService object lets you work with files and directories.
+ Following code creates a FileService object with storage account and SAS Token.
+
+
+var fileUri = 'https://' + 'STORAGE_ACCOUNT' + '.file.core.windows.net';
+var fileService = AzureStorage.File.createFileServiceWithSas(fileUri, 'SAS_TOKEN');
+
+
+ You can load Azure Storage JavaScript Client Library in a CommonJS or AMD environment by JavaScript module loaders. If no module system is found, global variable AzureStorage.File will be set, which is the start point where we can create service objects for file and access to the storage utilities.
+
+
+
+
How to get full detailed API definitions? Currently, the JavaScript Client Library shares almost the same API definitions with Node.js SDK, besides Node.js runtime specific APIs.
+ Please check API details on
Azure Storage API reference documents. The JavaScript global variable
AzureStorage.File is just like the object
require('azure-storage') returns in Node.js, but limits to File related interfaces.
+ Go to
FileService to view possible methods provided by
FileService class.
+
+
+
+
+
Warning: Azure Storage JavaScript Client Library also supports creating
FileService based on Storage Account Key for authentication besides SAS Token.
+ However, for security concerns, we recommend use of a limited time SAS Token, generated by a backend web server using a
Stored Access Policy.
+
+
+
+
Step 4: File Share Operations
+
Share: A File storage share is an SMB file share in Azure. All directories and files must be created in a parent share. An account can contain an unlimited number of shares, and a share can store an unlimited number of files, up to the 5 TB total capacity of the file share.
+
+
List File Shares
+
FileService provides listSharesSegmented and listSharesSegmentedWithPrefix for listing file shares under a storage account.
+
+fileService.listSharesSegmented(null, function(error, result) {
+ if(error) {
+ // List shares error
+ } else {
+ for (var i = 0, share; share = results.entries[i]; i++) {
+ // Deal with share object
+ }
+ }
+});
+
+
+
Create File Share
+
FileService provides createShare and createShareIfNotExists for creating a file share under a storage account.
+
+fileService.createShareIfNotExists('myshare', function(error, result) {
+ if(error) {
+ // Create share error
+ } else {
+ // Create share successfully
+ }
+});
+
+
+
Delete File Share
+
FileService provides deleteShare and deleteShareIfExists for deleting a file share under a storage account.
+
+fileService.deleteShareIfExists('myshare', function(error, result) {
+ if(error) {
+ // Delete share error
+ } else {
+ // Delete share successfully
+ }
+});
+
+
+
Executable Example
+
The sample will try to create an Azure Storage file service object based on SAS Token authorization. Enter your Azure Storage account name and SAS Token here. Make sure you have set the CORS rules for the Azure Storage file service, and the SAS Token is in valid period.
+
+
+
Azure Storage file service provides plenty of interfaces for file operations. In following example, you can try to list all the file shares under your storage account, and try to create or delete one file share from your account.
+
+ Click button to view the file share list under your Azure Storage account
-
+
Click button to create a file share under your Azure Storage account
+
+
+ Click "Delete" button to delete the file share under your Azure Storage account
Click "Select" button to operate with the directories and files in next step
+
+
+
Step 5: Directory and File Operations
+
Directory in storage is an optional hierarchy of directories.
+
File: A file in the share. A file may be up to 1 TB in size.
+
+
List Files and Directories
+
FileService provides listFilesAndDirectoriesSegmented for listing directories and files under a file share.
+
+fileService.listFilesAndDirectoriesSegmented('myfileshare', '', null, function(error, result, response) {
+ if(error) {
+ // List table entity error
+ } else {
+ for (var i = 0, dir; dir = results.entries.directories[i]; i++) {
+ // Deal with directory object
+ }
+ for (var i = 0, file; file = results.entries.files[i]; i++) {
+ // Deal with file object
+ }
+ }
+});
+
+
+
Create Directory
+
FileService provides createDirectory and createDirectoryIfNotExists for creating directories under a file share.
+
+fileService.createDirectoryIfNotExists('myfileshare', 'mydirectory', function(error, result, response) {
+ if(error) {
+ // Create directory error
+ } else {
+ // Create directory successfully
+ }
+});
+
+
+
Delete Directory
+
FileService provides deleteDirectory and deleteDirectoryIfExists for deleting directories under a file share.
+
+fileService.deleteDirectoryIfExists('myfileshare', 'mydirectory', function(error, result, response) {
+ if(error) {
+ // Delete directory error
+ } else {
+ // Delete directory successfully
+ }
+});
+
+
+
Upload File
+
FileService provides createFileFromBrowserFile for uploading a file from an HTML file in browsers.
+
+
+
Uploading file from stream. You can set up the file name as well as the size of this uploading session.
+
+// If one file has been selected in the HTML file input element
+var files = document.getElementById('fileinput').files;
+var file = files[0];
+
+var finishedOrError = false;
+var speedSummary = fileService.createFileFromBrowserFile('myfileshare', 'mydirectory', file.name, file, {}, function(error, result, response) {
+ finishedOrError = true;
+ if (error) {
+ // Upload file failed
+ } else {
+ // Upload successfully
+ }
+});
+refreshProgress();
+
+
Checking the upload progress with speedSummary object.
+
+speedSummary.on('progress', function () {
+ var process = speedSummary.getCompletePercent();
+ displayProcess(process);
+});
+
+
Download File
+
+ FileService provides interfaces for downloading a file into browser memory directly.
+ Because of browser's sandbox limitation, we cannot save the downloaded data trunks into disk until we get all the data trunks of a file into browser memory.
+ The browser's memory size is also limited especially for downloading huge files, so it's recommended to download a file in browser with SAS Token authorized link directly.
+
+
+ Shared access signatures (SAS) are a secure way to provide granular access to files and directories without providing your storage account name or keys. Shared access signatures are often used to provide limited access to your data, such as allowing a mobile app to access files.
+ The following code example generates a new shared access policy that allows the shared access signatures holder to perform read operations on the myfile file, and expires 100 minutes after the time it is created.
+
+
+
+ Note: You can choose to use the SAS Token in browser side, or generate a temporary SAS Token dynamically in your server side with Azure Storage C# or Node.js SDKs etc. according to your security requirements.
+
+
+
+var downloadLink = fileService.getUrl('myshare', 'mydirectory', 'myfile', 'SAS_TOKEN');
+
+
+
Delete File
+
FileService provides deleteFile and deleteFileIfExists for deleting files under a file share.
+
+fileService.deleteFileIfExists('myfileshare', 'mydirectory', 'myfile', function(error, result, response) {
+ if(error) {
+ // Delete file error
+ } else {
+ // Delete file successfully
+ }
+});
+
+
+
Executable Example
+
After clicked the "Select" button on the file share list, you are able to operate with the directories and files under the selected file share.
+
+ Click button to view the directories and files under your selected file share
Click button to create a directory share under your current directory
+
+ Click button to return to upper level directory
Click button to upload a local file to current directory
+ Click "Delete" button to delete the directory or file
Click "Download" link to download a file to local
+
+
Current Path:
+
Uploaded Bytes:
+
+
+
+
Step 6: Creating your JavaScript Application based on Azure Storage JavaScript Client Library
+
+ - Setting CORS rules for your selected Azure-Storage account file service.
+ - Including functional file(s) needed, such as "azure-storage.file.js" for file operation.
+ - Using keyword "AzureStorage.File" to access to Azure storage JavaScript APIs for files.
+ - Referring to API documents for detailed API definitions.
+
+
You can view the source code of this sample for detailed reference.
+
+
+
Azure Storage JavaScript Client Library Sample for Queue Operations
+
+
In this sample, we will demonstrate common scenarios for Azure Queue Storage that includes creating, listing and deleting queues and messages.
+
+
+
Azure Storage queue service provides cloud messaging between application components. In designing applications for scale, application components are often decoupled, so that they can scale independently. Queue storage delivers asynchronous messaging for communication between application components, whether they are running in the cloud, on the desktop, on an on-premises server, or on a mobile device. Queue storage also supports managing asynchronous tasks and building process work flows.
+
+
+
+
+ Note: You may need set up a HTTP server to host this sample for IE11 and latest Chrome.
+
+
+
+
Contents:
+
+
+
Step 1: Preparing an Azure Storage account with CORS rules set
+
Cross-origin resource sharing, or CORS, must be configured on the Azure Storage account to be accessed directly from JavaScript in the browser.
+ You are able to set the CORS rules for specific Azure Storage account on the Azure Portal.
+ The "Allowed origins" could be set to "*" to allow all the origins in this sample.
+ For more information about CORS, see Cross-Origin Resource Sharing (CORS).
+
+
+
Step 2: Importing Azure Storage JavaScript Client Library
+
+ Importing azure-storage.queue.js in your HTML file for queue operations.
+
+
+<script src="azure-storage.queue.js"></script>
+
+
+
Step 3: Creating an Azure Storage Queue Service Object
+
+ The QueueService object lets you work with queues and messages.
+ Following code creates a QueueService object with storage account and SAS Token.
+
+
+var queueUri = 'https://' + 'STORAGE_ACCOUNT' + '.queue.core.windows.net';
+var queueService = AzureStorage.Queue.createQueueServiceWithSas(queueUri, 'SAS_TOKEN');
+
+
+ You can load Azure Storage JavaScript Client Library in a CommonJS or AMD environment by JavaScript module loaders. If no module system is found, global variable AzureStorage.Queue will be set, which is the start point where we can create service objects for queue and access to the storage utilities.
+
+
+
+
How to get full detailed API definitions? Currently, the JavaScript Client Library shares almost the same API definitions with Node.js SDK, besides Node.js runtime specific APIs.
+ Please check API details on
Azure Storage API reference documents. The JavaScript global variable
AzureStorage.Queue is just like the object
require('azure-storage') returns in Node.js, but limits to Queue related interfaces.
+ Go to
QueueService to view possible methods provided by
QueueService class.
+
+
+
+
+
Warning: Azure Storage JavaScript Client Library also supports creating
QueueService based on Storage Account Key for authentication besides SAS Token.
+ However, for security concerns, we recommend use of a limited time SAS Token, generated by a backend web server using a
Stored Access Policy.
+
+
+
+
Step 4: Queue Operations
+
+ Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. A single queue message can be up to 64 KB in size, and a queue can contain millions of messages, up to the total capacity limit of a storage account.
+
+
+
List Queues
+
QueueService provides listQueuesSegmented and listQueuesSegmentedWithPrefix for retrieving the queue list under your storage account.
+
+queueService.listQueuesSegmented(null, function (error, results) {
+ if (error) {
+ // List queue error
+ } else {
+ for (var i = 0, queue; queue = results.entries[i]; i++) {
+ // Deal with queue object
+ }
+ }
+});
+
+
+
Create Queue
+
QueueService provides createQueue and createQueueIfNotExists for creating a queue under a storage account.
+
+queueService.createQueueIfNotExists('myqueue', function(error, result) {
+ if (error) {
+ // Create queue error
+ } else {
+ // Create queue successfully
+ }
+});
+
+
+
Delete Queue
+
QueueService provides deleteQueue and deleteQueueIfExists for deleting a queue under a storage account.
+
+queueService.deleteQueueIfExists('myqueue', function(error, result) {
+ if (error) {
+ // Delete queue error
+ } else {
+ // Delete queue successfully
+ }
+});
+
+
+
Executable Example
+
The sample will try to create an Azure Storage queue service object based on SAS Token authorization. Enter your Azure Storage account name and SAS Token here. Make sure you have set the CORS rules for the Azure Storage queue service, and the SAS Token is in valid period.
+
+
+
Azure Storage queue service provides plenty of interfaces for queue operations. In following example, you can try to list all the queues under your storage account, and try to create or delete one queue from your account.
+
+ Click button to view the queue list under your Azure Storage account
Click button to create a queue under your Azure Storage account:
+
+ Click "Delete" button to delete the queue under your Azure Storage account
Click "Select" button to select a queue and operate with the queue messages in next step
+
+
+
Step 5: Message Operations
+
A storage Message, in any format, of up to 64 KB. The maximum time that a message can remain in the queue is 7 days.
+
+
+ Note: Azure Storage JavaScript Client Library provides var encoder = new AzureStorage.Queue.QueueMessageEncoder.TextBase64QueueMessageEncoder() which is a Base64 encoder and docoder.
+ If a message content string is encoded with encoder.encode(), remember to decode it with encoder.decode() after peek the message.
+
+
+
+
Peek Messages
+
QueueService provides peekMessage and peekMessages for retrieving the messages list under a queue.
+
+queueService.peekMessages('myqueue', {numOfMessages: 32}, function (error, results) {
+ if (error) {
+ // Peek messages error
+ } else {
+ for (var i = 0, message; message = results[i]; i++) {
+ // Deal with message object
+ }
+ }
+});
+
+
+
Create Message
+
QueueService provides createMessage for creating a new message to a queue.
+
+var encoder = new AzureStorage.Queue.QueueMessageEncoder.TextBase64QueueMessageEncoder();
+queueService.createMessage('myqueue', encoder.encode('mymessage'), function (error, results, response) {
+ if (error) {
+ // Create message error
+ } else {
+ // Create message successfully
+ }
+});
+
+
+
Dequeue Message
+
QueueService provides getMessages and deleteMessage for dequeuing next message in a queue.
+
+queueService.getMessages('myqueue', function(error, result, response) {
+ if(!error){
+ // Message text is in messages[0].messageText
+ var message = result[0];
+ queueService.deleteMessage('myqueue', message.messageId, message.popReceipt, function(error, response){
+ if(!error){
+ //message deleted
+ }
+ });
+ }
+});
+
+
+
Update Message
+
QueueService provides getMessages and updateMessage for updating next message in a queue.
+
+var encoder = new AzureStorage.Queue.QueueMessageEncoder.TextBase64QueueMessageEncoder();
+queueService.getMessages('myqueue', function(error, result, response) {
+ if(!error){
+ // Got the message
+ var message = result[0];
+ queueService.updateMessage('myqueue', message.messageId, message.popReceipt, 10, {messageText: encoder.encode('new text')}, function(error, result, response){
+ if(!error){
+ // Message updated successfully
+ }
+ });
+ }
+});
+
+
+
Executable Example
+
After clicked the "Select" button on the queue list in last step, you are able to operate with the queue messages under the selected queue.
+
+ Click button to refresh the message list in your selected queue
Click button to create a message in your selected queue:
+
+ Click button to update the top queue message in your selected queue (Dequeued messages will be invisible for 30s by default.):
+
+ Click button to dequeue the top queue message in your selected queue:
+
+
+
+
Step 6: Creating your JavaScript Application based on Azure Storage JavaScript Client Library
+
+ - Setting CORS rules for your selected Azure-Storage account queue service.
+ - Including functional file(s) needed, such as "azure-storage.queue.js" for queue operation.
+ - Using keyword "AzureStorage.Queue" to access to Azure storage JavaScript APIs for queues.
+ - Referring to API documents for detailed API definitions.
+
+
You can view the source code of this sample for detailed reference.
+
+
+
Azure Storage JavaScript Client Library Sample for Table Operations
+
+
In this sample, we will demonstrate common scenarios for Azure Table Storage that includes creating, listing and deleting tables and entities.
+
+
+
Azure Storage table is a service that stores structured NoSQL data in the cloud. Table storage is a key/attribute store with a schemaless design. Because Table storage is schemaless, it's easy to adapt your data as the needs of your application evolve. Access to data is fast and cost-effective for all kinds of applications. Table storage is typically significantly lower in cost than traditional SQL for similar volumes of data.
+
+
+
+
+ Note: You may need set up a HTTP server to host this sample for IE11 and latest Chrome.
+
+
+
+
Contents:
+
+
+
Step 1: Preparing an Azure Storage account with CORS rules set
+
Cross-origin resource sharing, or CORS, must be configured on the Azure Storage account to be accessed directly from JavaScript in the browser.
+ You are able to set the CORS rules for specific Azure Storage account on the Azure Portal.
+ The "Allowed origins" could be set to "*" to allow all the origins in this sample.
+ For more information about CORS, see Cross-Origin Resource Sharing (CORS).
+
+
+
Step 2: Importing Azure Storage JavaScript Client Library
+
+ Importing azure-storage.table.js in your HTML file for table operations.
+
+
+<script src="azure-storage.table.js"></script>
+
+
+
Step 3: Creating an Azure Storage Table Service Object
+
+ The TableService object lets you work with table and entities.
+ Following code creates a TableService object with storage account and SAS Token.
+
+
+var tableUri = 'https://' + 'STORAGE_ACCOUNT' + '.table.core.windows.net';
+var tableService = AzureStorage.Table.createTableServiceWithSas(tableUri, 'SAS_TOKEN');
+
+
+ You can load Azure Storage JavaScript Client Library in a CommonJS or AMD environment by JavaScript module loaders. If no module system is found, global variable AzureStorage.Table will be set, which is the start point where we can create service objects for table and access to the storage utilities.
+
+
+
+
How to get full detailed API definitions? Currently, the JavaScript Client Library shares almost the same API definitions with Node.js SDK, besides Node.js runtime specific APIs.
+ Please check API details on
Azure Storage API reference documents. The JavaScript global variable
AzureStorage.Table is just like the object
require('azure-storage') returns in Node.js, but limits to Table related interfaces.
+ Go to
TableService to view possible methods provided by
TableService class.
+
+
+
+
+
Warning: Azure Storage JavaScript Client Library also supports creating
TableService based on Storage Account Key for authentication besides SAS Token.
+ However, for security concerns, we recommend use of a limited time SAS Token, generated by a backend web server using a
Stored Access Policy.
+
+
+
+
Step 4: Table Operations
+
+ Table: A table is a collection of entities. Tables don't enforce a schema on entities, which means a single table can contain entities that have different sets of properties. The number of tables that a storage account can contain is limited only by the storage account capacity limit.
+
+
+
List Tables
+
TableService provides listTablesSegmented and listTablesSegmentedWithPrefix for retrieving the table list under your storage account.
+
+tableService.listTablesSegmented(null, {maxResults : 200}, function (error, results) {
+ if (error) {
+ // List tables error
+ } else {
+ for (var i = 0, table; table = results.entries[i]; i++) {
+ // Deal with table object
+ }
+ }
+});
+
+
+
Create Table
+
TableService provides createTable and createTableIfNotExists for creating a table under a storage account.
+
+tableService.createTableIfNotExists('mytable', function(error, result) {
+ if (error) {
+ // Create table error
+ } else {
+ // Create table successfully
+ }
+});
+
+
+
Delete Table
+
TableService provides deleteTable and deleteTableIfExists for deleting a table under a storage account.
+
+tableService.deleteTableIfExists('mytable', function(error, result) {
+ if (error) {
+ // Delete table error
+ } else {
+ // Delete table successfully
+ }
+});
+
+
+
Executable Example
+
The sample will try to create an Azure Storage table service object based on SAS Token authorization. Enter your Azure Storage account name and SAS Token here. Make sure you have set the CORS rules for the Azure Storage table service, and the SAS Token is in valid period.
+
+
+
Azure Storage table service provides plenty of interfaces for table operations. In following example, you can try to list all the tables under your storage account, and try to create or delete one table from your account.
+
+ Click button to view the table list under your Azure Storage account
Click button to create a table under your Azure Storage account
+
+ Click "Delete" button to delete the table under your Azure Storage account
Click "Select" button to operate with the table entities in next step
+
+
+
Step 5: Table Entities Operations
+
Entity: An entity is a set of properties, similar to a database row. An entity can be up to 1MB in size.
+
Properties: A property is a name-value pair. Each entity can include up to 252 properties to store data. Each entity also has 3 system properties that specify a partition key, a row key, and a timestamp. Entities with the same partition key can be queried more quickly, and inserted/updated in atomic operations. An entity's row key is its unique identifier within a partition.
+
+
Query Entities
+
TableService provides queryEntities for querying a table under a storage account.
+
+var tableQuery = new AzureStorage.Table.TableQuery().top(200);
+tableService.queryEntities('mytable', tableQuery, null, function(error, result) {
+ if (error) {
+ // Query entities error
+ } else {
+ for (var i = 0, entity; entity = results.entries[i]; i++) {
+ // Deal with entity object
+ }
+ }
+});
+
+
+
Insert or Replace Entity
+
TableService provides insertEntity, insertOrReplaceEntity and insertOrMergeEntity for adding a table entity under a storage account.
+
+var insertEntity = {
+ PartitionKey: {'_': 'partitionKey'},
+ RowKey: {'_': 'rowKey'}
+};
+
+tableService.insertOrReplaceEntity('mytable', insertEntity, function(error, result, response) {
+ if(error) {
+ // Insert table entity error
+ } else {
+ // Insert table entity successfully
+ }
+});
+
+
+
Delete Entity
+
TableService provides deleteEntity for deleting a table entity under a storage account.
+
+var deleteEntity = {
+ PartitionKey: {'_': 'partitionKey'},
+ RowKey: {'_': 'rowKey'}
+};
+
+tableService.deleteEntity('mytable', deleteEntity, function(error, result, response) {
+ if(error) {
+ // Delete table entity error
+ } else {
+ // Delete table entity successfully
+ }
+});
+
+
+
Executable Example
+
After clicked the "Select" button on the table list, you are able to operate with the table entities under the selected table.
+
+
+
+
Step 6: Creating your JavaScript Application based on Azure Storage JavaScript Client Library
+
+ - Setting CORS rules for your selected Azure-Storage account table service.
+ - Including functional file(s) needed, such as "azure-storage.table.js" for table operation.
+ - Using keyword "AzureStorage.Table" to access to Azure storage JavaScript APIs for tables.
+ - Referring to API documents for detailed API definitions.
+
+
You can view the source code of this sample for detailed reference.
+
+
+# Ajv: Another JSON Schema Validator
+
+The fastest JSON Schema validator for Node.js and browser. Supports draft-04/06/07.
+
+[](https://travis-ci.org/epoberezkin/ajv)
+[](https://www.npmjs.com/package/ajv)
+[](https://www.npmjs.com/package/ajv)
+[](https://coveralls.io/github/epoberezkin/ajv?branch=master)
+[](https://greenkeeper.io/)
+[](https://gitter.im/ajv-validator/ajv)
+
+### _Ajv and [related repositories](#related-packages) will be transfered to [ajv-validator](https://github.com/ajv-validator) org_
+
+## Using version 6
+
+[JSON Schema draft-07](http://json-schema.org/latest/json-schema-validation.html) is published.
+
+[Ajv version 6.0.0](https://github.com/epoberezkin/ajv/releases/tag/v6.0.0) that supports draft-07 is released. It may require either migrating your schemas or updating your code (to continue using draft-04 and v5 schemas, draft-06 schemas will be supported without changes).
+
+__Please note__: To use Ajv with draft-06 schemas you need to explicitly add the meta-schema to the validator instance:
+
+```javascript
+ajv.addMetaSchema(require('ajv/lib/refs/json-schema-draft-06.json'));
+```
+
+To use Ajv with draft-04 schemas in addition to explicitly adding meta-schema you also need to use option schemaId:
+
+```javascript
+var ajv = new Ajv({schemaId: 'id'});
+// If you want to use both draft-04 and draft-06/07 schemas:
+// var ajv = new Ajv({schemaId: 'auto'});
+ajv.addMetaSchema(require('ajv/lib/refs/json-schema-draft-04.json'));
+```
+
+
+## Contents
+
+- [Performance](#performance)
+- [Features](#features)
+- [Getting started](#getting-started)
+- [Frequently Asked Questions](https://github.com/epoberezkin/ajv/blob/master/FAQ.md)
+- [Using in browser](#using-in-browser)
+- [Command line interface](#command-line-interface)
+- Validation
+ - [Keywords](#validation-keywords)
+ - [Annotation keywords](#annotation-keywords)
+ - [Formats](#formats)
+ - [Combining schemas with $ref](#ref)
+ - [$data reference](#data-reference)
+ - NEW: [$merge and $patch keywords](#merge-and-patch-keywords)
+ - [Defining custom keywords](#defining-custom-keywords)
+ - [Asynchronous schema compilation](#asynchronous-schema-compilation)
+ - [Asynchronous validation](#asynchronous-validation)
+ - [Security considerations](#security-considerations)
+- Modifying data during validation
+ - [Filtering data](#filtering-data)
+ - [Assigning defaults](#assigning-defaults)
+ - [Coercing data types](#coercing-data-types)
+- API
+ - [Methods](#api)
+ - [Options](#options)
+ - [Validation errors](#validation-errors)
+- [Plugins](#plugins)
+- [Related packages](#related-packages)
+- [Some packages using Ajv](#some-packages-using-ajv)
+- [Tests, Contributing, History, License](#tests)
+
+
+## Performance
+
+Ajv generates code using [doT templates](https://github.com/olado/doT) to turn JSON Schemas into super-fast validation functions that are efficient for v8 optimization.
+
+Currently Ajv is the fastest and the most standard compliant validator according to these benchmarks:
+
+- [json-schema-benchmark](https://github.com/ebdrup/json-schema-benchmark) - 50% faster than the second place
+- [jsck benchmark](https://github.com/pandastrike/jsck#benchmarks) - 20-190% faster
+- [z-schema benchmark](https://rawgit.com/zaggino/z-schema/master/benchmark/results.html)
+- [themis benchmark](https://cdn.rawgit.com/playlyfe/themis/master/benchmark/results.html)
+
+
+Performance of different validators by [json-schema-benchmark](https://github.com/ebdrup/json-schema-benchmark):
+
+[](https://github.com/ebdrup/json-schema-benchmark/blob/master/README.md#performance)
+
+
+## Features
+
+- Ajv implements full JSON Schema [draft-06/07](http://json-schema.org/) and draft-04 standards:
+ - all validation keywords (see [JSON Schema validation keywords](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md))
+ - full support of remote refs (remote schemas have to be added with `addSchema` or compiled to be available)
+ - support of circular references between schemas
+ - correct string lengths for strings with unicode pairs (can be turned off)
+ - [formats](#formats) defined by JSON Schema draft-07 standard and custom formats (can be turned off)
+ - [validates schemas against meta-schema](#api-validateschema)
+- supports [browsers](#using-in-browser) and Node.js 0.10-8.x
+- [asynchronous loading](#asynchronous-schema-compilation) of referenced schemas during compilation
+- "All errors" validation mode with [option allErrors](#options)
+- [error messages with parameters](#validation-errors) describing error reasons to allow creating custom error messages
+- i18n error messages support with [ajv-i18n](https://github.com/epoberezkin/ajv-i18n) package
+- [filtering data](#filtering-data) from additional properties
+- [assigning defaults](#assigning-defaults) to missing properties and items
+- [coercing data](#coercing-data-types) to the types specified in `type` keywords
+- [custom keywords](#defining-custom-keywords)
+- draft-06/07 keywords `const`, `contains`, `propertyNames` and `if/then/else`
+- draft-06 boolean schemas (`true`/`false` as a schema to always pass/fail).
+- keywords `switch`, `patternRequired`, `formatMaximum` / `formatMinimum` and `formatExclusiveMaximum` / `formatExclusiveMinimum` from [JSON Schema extension proposals](https://github.com/json-schema/json-schema/wiki/v5-Proposals) with [ajv-keywords](https://github.com/epoberezkin/ajv-keywords) package
+- [$data reference](#data-reference) to use values from the validated data as values for the schema keywords
+- [asynchronous validation](#asynchronous-validation) of custom formats and keywords
+
+Currently Ajv is the only validator that passes all the tests from [JSON Schema Test Suite](https://github.com/json-schema/JSON-Schema-Test-Suite) (according to [json-schema-benchmark](https://github.com/ebdrup/json-schema-benchmark), apart from the test that requires that `1.0` is not an integer that is impossible to satisfy in JavaScript).
+
+
+## Install
+
+```
+npm install ajv
+```
+
+
+## Getting started
+
+Try it in the Node.js REPL: https://tonicdev.com/npm/ajv
+
+
+The fastest validation call:
+
+```javascript
+var Ajv = require('ajv');
+var ajv = new Ajv(); // options can be passed, e.g. {allErrors: true}
+var validate = ajv.compile(schema);
+var valid = validate(data);
+if (!valid) console.log(validate.errors);
+```
+
+or with less code
+
+```javascript
+// ...
+var valid = ajv.validate(schema, data);
+if (!valid) console.log(ajv.errors);
+// ...
+```
+
+or
+
+```javascript
+// ...
+var valid = ajv.addSchema(schema, 'mySchema')
+ .validate('mySchema', data);
+if (!valid) console.log(ajv.errorsText());
+// ...
+```
+
+See [API](#api) and [Options](#options) for more details.
+
+Ajv compiles schemas to functions and caches them in all cases (using schema serialized with [fast-json-stable-stringify](https://github.com/epoberezkin/fast-json-stable-stringify) or a custom function as a key), so that the next time the same schema is used (not necessarily the same object instance) it won't be compiled again.
+
+The best performance is achieved when using compiled functions returned by `compile` or `getSchema` methods (there is no additional function call).
+
+__Please note__: every time a validation function or `ajv.validate` are called `errors` property is overwritten. You need to copy `errors` array reference to another variable if you want to use it later (e.g., in the callback). See [Validation errors](#validation-errors)
+
+
+## Using in browser
+
+You can require Ajv directly from the code you browserify - in this case Ajv will be a part of your bundle.
+
+If you need to use Ajv in several bundles you can create a separate UMD bundle using `npm run bundle` script (thanks to [siddo420](https://github.com/siddo420)).
+
+Then you need to load Ajv in the browser:
+```html
+
+```
+
+This bundle can be used with different module systems; it creates global `Ajv` if no module system is found.
+
+The browser bundle is available on [cdnjs](https://cdnjs.com/libraries/ajv).
+
+Ajv is tested with these browsers:
+
+[](https://saucelabs.com/u/epoberezkin)
+
+__Please note__: some frameworks, e.g. Dojo, may redefine global require in such way that is not compatible with CommonJS module format. In such case Ajv bundle has to be loaded before the framework and then you can use global Ajv (see issue [#234](https://github.com/epoberezkin/ajv/issues/234)).
+
+
+## Command line interface
+
+CLI is available as a separate npm package [ajv-cli](https://github.com/jessedc/ajv-cli). It supports:
+
+- compiling JSON Schemas to test their validity
+- BETA: generating standalone module exporting a validation function to be used without Ajv (using [ajv-pack](https://github.com/epoberezkin/ajv-pack))
+- migrate schemas to draft-07 (using [json-schema-migrate](https://github.com/epoberezkin/json-schema-migrate))
+- validating data file(s) against JSON Schema
+- testing expected validity of data against JSON Schema
+- referenced schemas
+- custom meta-schemas
+- files in JSON and JavaScript format
+- all Ajv options
+- reporting changes in data after validation in [JSON-patch](https://tools.ietf.org/html/rfc6902) format
+
+
+## Validation keywords
+
+Ajv supports all validation keywords from draft-07 of JSON Schema standard:
+
+- [type](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#type)
+- [for numbers](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#keywords-for-numbers) - maximum, minimum, exclusiveMaximum, exclusiveMinimum, multipleOf
+- [for strings](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#keywords-for-strings) - maxLength, minLength, pattern, format
+- [for arrays](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#keywords-for-arrays) - maxItems, minItems, uniqueItems, items, additionalItems, [contains](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#contains)
+- [for objects](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#keywords-for-objects) - maxProperties, minProperties, required, properties, patternProperties, additionalProperties, dependencies, [propertyNames](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#propertynames)
+- [for all types](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#keywords-for-all-types) - enum, [const](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#const)
+- [compound keywords](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#compound-keywords) - not, oneOf, anyOf, allOf, [if/then/else](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#ifthenelse)
+
+With [ajv-keywords](https://github.com/epoberezkin/ajv-keywords) package Ajv also supports validation keywords from [JSON Schema extension proposals](https://github.com/json-schema/json-schema/wiki/v5-Proposals) for JSON Schema standard:
+
+- [patternRequired](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#patternrequired-proposed) - like `required` but with patterns that some property should match.
+- [formatMaximum, formatMinimum, formatExclusiveMaximum, formatExclusiveMinimum](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md#formatmaximum--formatminimum-and-exclusiveformatmaximum--exclusiveformatminimum-proposed) - setting limits for date, time, etc.
+
+See [JSON Schema validation keywords](https://github.com/epoberezkin/ajv/blob/master/KEYWORDS.md) for more details.
+
+
+## Annotation keywords
+
+JSON Schema specification defines several annotation keywords that describe schema itself but do not perform any validation.
+
+- `title` and `description`: information about the data represented by that schema
+- `$comment` (NEW in draft-07): information for developers. With option `$comment` Ajv logs or passes the comment string to the user-supplied function. See [Options](#options).
+- `default`: a default value of the data instance, see [Assigning defaults](#assigning-defaults).
+- `examples` (NEW in draft-07): an array of data instances. Ajv does not check the validity of these instances against the schema.
+- `readOnly` and `writeOnly` (NEW in draft-07): marks data-instance as read-only or write-only in relation to the source of the data (database, api, etc.).
+- `contentEncoding`: [RFC 2045](https://tools.ietf.org/html/rfc2045#section-6.1 ), e.g., "base64".
+- `contentMediaType`: [RFC 2046](https://tools.ietf.org/html/rfc2046), e.g., "image/png".
+
+__Please note__: Ajv does not implement validation of the keywords `examples`, `contentEncoding` and `contentMediaType` but it reserves them. If you want to create a plugin that implements some of them, it should remove these keywords from the instance.
+
+
+## Formats
+
+The following formats are supported for string validation with "format" keyword:
+
+- _date_: full-date according to [RFC3339](http://tools.ietf.org/html/rfc3339#section-5.6).
+- _time_: time with optional time-zone.
+- _date-time_: date-time from the same source (time-zone is mandatory). `date`, `time` and `date-time` validate ranges in `full` mode and only regexp in `fast` mode (see [options](#options)).
+- _uri_: full URI.
+- _uri-reference_: URI reference, including full and relative URIs.
+- _uri-template_: URI template according to [RFC6570](https://tools.ietf.org/html/rfc6570)
+- _url_ (deprecated): [URL record](https://url.spec.whatwg.org/#concept-url).
+- _email_: email address.
+- _hostname_: host name according to [RFC1034](http://tools.ietf.org/html/rfc1034#section-3.5).
+- _ipv4_: IP address v4.
+- _ipv6_: IP address v6.
+- _regex_: tests whether a string is a valid regular expression by passing it to RegExp constructor.
+- _uuid_: Universally Unique IDentifier according to [RFC4122](http://tools.ietf.org/html/rfc4122).
+- _json-pointer_: JSON-pointer according to [RFC6901](https://tools.ietf.org/html/rfc6901).
+- _relative-json-pointer_: relative JSON-pointer according to [this draft](http://tools.ietf.org/html/draft-luff-relative-json-pointer-00).
+
+__Please note__: JSON Schema draft-07 also defines formats `iri`, `iri-reference`, `idn-hostname` and `idn-email` for URLs, hostnames and emails with international characters. Ajv does not implement these formats. If you create Ajv plugin that implements them please make a PR to mention this plugin here.
+
+There are two modes of format validation: `fast` and `full`. This mode affects formats `date`, `time`, `date-time`, `uri`, `uri-reference`, `email`, and `hostname`. See [Options](#options) for details.
+
+You can add additional formats and replace any of the formats above using [addFormat](#api-addformat) method.
+
+The option `unknownFormats` allows changing the default behaviour when an unknown format is encountered. In this case Ajv can either fail schema compilation (default) or ignore it (default in versions before 5.0.0). You also can whitelist specific format(s) to be ignored. See [Options](#options) for details.
+
+You can find regular expressions used for format validation and the sources that were used in [formats.js](https://github.com/epoberezkin/ajv/blob/master/lib/compile/formats.js).
+
+
+## Combining schemas with $ref
+
+You can structure your validation logic across multiple schema files and have schemas reference each other using `$ref` keyword.
+
+Example:
+
+```javascript
+var schema = {
+ "$id": "http://example.com/schemas/schema.json",
+ "type": "object",
+ "properties": {
+ "foo": { "$ref": "defs.json#/definitions/int" },
+ "bar": { "$ref": "defs.json#/definitions/str" }
+ }
+};
+
+var defsSchema = {
+ "$id": "http://example.com/schemas/defs.json",
+ "definitions": {
+ "int": { "type": "integer" },
+ "str": { "type": "string" }
+ }
+};
+```
+
+Now to compile your schema you can either pass all schemas to Ajv instance:
+
+```javascript
+var ajv = new Ajv({schemas: [schema, defsSchema]});
+var validate = ajv.getSchema('http://example.com/schemas/schema.json');
+```
+
+or use `addSchema` method:
+
+```javascript
+var ajv = new Ajv;
+var validate = ajv.addSchema(defsSchema)
+ .compile(schema);
+```
+
+See [Options](#options) and [addSchema](#api) method.
+
+__Please note__:
+- `$ref` is resolved as the uri-reference using schema $id as the base URI (see the example).
+- References can be recursive (and mutually recursive) to implement the schemas for different data structures (such as linked lists, trees, graphs, etc.).
+- You don't have to host your schema files at the URIs that you use as schema $id. These URIs are only used to identify the schemas, and according to JSON Schema specification validators should not expect to be able to download the schemas from these URIs.
+- The actual location of the schema file in the file system is not used.
+- You can pass the identifier of the schema as the second parameter of `addSchema` method or as a property name in `schemas` option. This identifier can be used instead of (or in addition to) schema $id.
+- You cannot have the same $id (or the schema identifier) used for more than one schema - the exception will be thrown.
+- You can implement dynamic resolution of the referenced schemas using `compileAsync` method. In this way you can store schemas in any system (files, web, database, etc.) and reference them without explicitly adding to Ajv instance. See [Asynchronous schema compilation](#asynchronous-schema-compilation).
+
+
+## $data reference
+
+With `$data` option you can use values from the validated data as the values for the schema keywords. See [proposal](https://github.com/json-schema/json-schema/wiki/$data-(v5-proposal)) for more information about how it works.
+
+`$data` reference is supported in the keywords: const, enum, format, maximum/minimum, exclusiveMaximum / exclusiveMinimum, maxLength / minLength, maxItems / minItems, maxProperties / minProperties, formatMaximum / formatMinimum, formatExclusiveMaximum / formatExclusiveMinimum, multipleOf, pattern, required, uniqueItems.
+
+The value of "$data" should be a [JSON-pointer](https://tools.ietf.org/html/rfc6901) to the data (the root is always the top level data object, even if the $data reference is inside a referenced subschema) or a [relative JSON-pointer](http://tools.ietf.org/html/draft-luff-relative-json-pointer-00) (it is relative to the current point in data; if the $data reference is inside a referenced subschema it cannot point to the data outside of the root level for this subschema).
+
+Examples.
+
+This schema requires that the value in property `smaller` is less or equal than the value in the property larger:
+
+```javascript
+var ajv = new Ajv({$data: true});
+
+var schema = {
+ "properties": {
+ "smaller": {
+ "type": "number",
+ "maximum": { "$data": "1/larger" }
+ },
+ "larger": { "type": "number" }
+ }
+};
+
+var validData = {
+ smaller: 5,
+ larger: 7
+};
+
+ajv.validate(schema, validData); // true
+```
+
+This schema requires that the properties have the same format as their field names:
+
+```javascript
+var schema = {
+ "additionalProperties": {
+ "type": "string",
+ "format": { "$data": "0#" }
+ }
+};
+
+var validData = {
+ 'date-time': '1963-06-19T08:30:06.283185Z',
+ email: 'joe.bloggs@example.com'
+}
+```
+
+`$data` reference is resolved safely - it won't throw even if some property is undefined. If `$data` resolves to `undefined` the validation succeeds (with the exclusion of `const` keyword). If `$data` resolves to incorrect type (e.g. not "number" for maximum keyword) the validation fails.
+
+
+## $merge and $patch keywords
+
+With the package [ajv-merge-patch](https://github.com/epoberezkin/ajv-merge-patch) you can use the keywords `$merge` and `$patch` that allow extending JSON Schemas with patches using formats [JSON Merge Patch (RFC 7396)](https://tools.ietf.org/html/rfc7396) and [JSON Patch (RFC 6902)](https://tools.ietf.org/html/rfc6902).
+
+To add keywords `$merge` and `$patch` to Ajv instance use this code:
+
+```javascript
+require('ajv-merge-patch')(ajv);
+```
+
+Examples.
+
+Using `$merge`:
+
+```json
+{
+ "$merge": {
+ "source": {
+ "type": "object",
+ "properties": { "p": { "type": "string" } },
+ "additionalProperties": false
+ },
+ "with": {
+ "properties": { "q": { "type": "number" } }
+ }
+ }
+}
+```
+
+Using `$patch`:
+
+```json
+{
+ "$patch": {
+ "source": {
+ "type": "object",
+ "properties": { "p": { "type": "string" } },
+ "additionalProperties": false
+ },
+ "with": [
+ { "op": "add", "path": "/properties/q", "value": { "type": "number" } }
+ ]
+ }
+}
+```
+
+The schemas above are equivalent to this schema:
+
+```json
+{
+ "type": "object",
+ "properties": {
+ "p": { "type": "string" },
+ "q": { "type": "number" }
+ },
+ "additionalProperties": false
+}
+```
+
+The properties `source` and `with` in the keywords `$merge` and `$patch` can use absolute or relative `$ref` to point to other schemas previously added to the Ajv instance or to the fragments of the current schema.
+
+See the package [ajv-merge-patch](https://github.com/epoberezkin/ajv-merge-patch) for more information.
+
+
+## Defining custom keywords
+
+The advantages of using custom keywords are:
+
+- allow creating validation scenarios that cannot be expressed using JSON Schema
+- simplify your schemas
+- help bringing a bigger part of the validation logic to your schemas
+- make your schemas more expressive, less verbose and closer to your application domain
+- implement custom data processors that modify your data (`modifying` option MUST be used in keyword definition) and/or create side effects while the data is being validated
+
+If a keyword is used only for side-effects and its validation result is pre-defined, use option `valid: true/false` in keyword definition to simplify both generated code (no error handling in case of `valid: true`) and your keyword functions (no need to return any validation result).
+
+The concerns you have to be aware of when extending JSON Schema standard with custom keywords are the portability and understanding of your schemas. You will have to support these custom keywords on other platforms and to properly document these keywords so that everybody can understand them in your schemas.
+
+You can define custom keywords with [addKeyword](#api-addkeyword) method. Keywords are defined on the `ajv` instance level - new instances will not have previously defined keywords.
+
+Ajv allows defining keywords with:
+- validation function
+- compilation function
+- macro function
+- inline compilation function that should return code (as string) that will be inlined in the currently compiled schema.
+
+Example. `range` and `exclusiveRange` keywords using compiled schema:
+
+```javascript
+ajv.addKeyword('range', {
+ type: 'number',
+ compile: function (sch, parentSchema) {
+ var min = sch[0];
+ var max = sch[1];
+
+ return parentSchema.exclusiveRange === true
+ ? function (data) { return data > min && data < max; }
+ : function (data) { return data >= min && data <= max; }
+ }
+});
+
+var schema = { "range": [2, 4], "exclusiveRange": true };
+var validate = ajv.compile(schema);
+console.log(validate(2.01)); // true
+console.log(validate(3.99)); // true
+console.log(validate(2)); // false
+console.log(validate(4)); // false
+```
+
+Several custom keywords (typeof, instanceof, range and propertyNames) are defined in [ajv-keywords](https://github.com/epoberezkin/ajv-keywords) package - they can be used for your schemas and as a starting point for your own custom keywords.
+
+See [Defining custom keywords](https://github.com/epoberezkin/ajv/blob/master/CUSTOM.md) for more details.
+
+
+## Asynchronous schema compilation
+
+During asynchronous compilation remote references are loaded using supplied function. See `compileAsync` [method](#api-compileAsync) and `loadSchema` [option](#options).
+
+Example:
+
+```javascript
+var ajv = new Ajv({ loadSchema: loadSchema });
+
+ajv.compileAsync(schema).then(function (validate) {
+ var valid = validate(data);
+ // ...
+});
+
+function loadSchema(uri) {
+ return request.json(uri).then(function (res) {
+ if (res.statusCode >= 400)
+ throw new Error('Loading error: ' + res.statusCode);
+ return res.body;
+ });
+}
+```
+
+__Please note__: [Option](#options) `missingRefs` should NOT be set to `"ignore"` or `"fail"` for asynchronous compilation to work.
+
+
+## Asynchronous validation
+
+Example in Node.js REPL: https://tonicdev.com/esp/ajv-asynchronous-validation
+
+You can define custom formats and keywords that perform validation asynchronously by accessing database or some other service. You should add `async: true` in the keyword or format definition (see [addFormat](#api-addformat), [addKeyword](#api-addkeyword) and [Defining custom keywords](#defining-custom-keywords)).
+
+If your schema uses asynchronous formats/keywords or refers to some schema that contains them it should have `"$async": true` keyword so that Ajv can compile it correctly. If asynchronous format/keyword or reference to asynchronous schema is used in the schema without `$async` keyword Ajv will throw an exception during schema compilation.
+
+__Please note__: all asynchronous subschemas that are referenced from the current or other schemas should have `"$async": true` keyword as well, otherwise the schema compilation will fail.
+
+Validation function for an asynchronous custom format/keyword should return a promise that resolves with `true` or `false` (or rejects with `new Ajv.ValidationError(errors)` if you want to return custom errors from the keyword function).
+
+Ajv compiles asynchronous schemas to [es7 async functions](http://tc39.github.io/ecmascript-asyncawait/) that can optionally be transpiled with [nodent](https://github.com/MatAtBread/nodent). Async functions are supported in Node.js 7+ and all modern browsers. You can also supply any other transpiler as a function via `processCode` option. See [Options](#options).
+
+The compiled validation function has `$async: true` property (if the schema is asynchronous), so you can differentiate these functions if you are using both synchronous and asynchronous schemas.
+
+Validation result will be a promise that resolves with validated data or rejects with an exception `Ajv.ValidationError` that contains the array of validation errors in `errors` property.
+
+
+Example:
+
+```javascript
+var ajv = new Ajv;
+// require('ajv-async')(ajv);
+
+ajv.addKeyword('idExists', {
+ async: true,
+ type: 'number',
+ validate: checkIdExists
+});
+
+
+function checkIdExists(schema, data) {
+ return knex(schema.table)
+ .select('id')
+ .where('id', data)
+ .then(function (rows) {
+ return !!rows.length; // true if record is found
+ });
+}
+
+var schema = {
+ "$async": true,
+ "properties": {
+ "userId": {
+ "type": "integer",
+ "idExists": { "table": "users" }
+ },
+ "postId": {
+ "type": "integer",
+ "idExists": { "table": "posts" }
+ }
+ }
+};
+
+var validate = ajv.compile(schema);
+
+validate({ userId: 1, postId: 19 })
+.then(function (data) {
+ console.log('Data is valid', data); // { userId: 1, postId: 19 }
+})
+.catch(function (err) {
+ if (!(err instanceof Ajv.ValidationError)) throw err;
+ // data is invalid
+ console.log('Validation errors:', err.errors);
+});
+```
+
+### Using transpilers with asynchronous validation functions.
+
+[ajv-async](https://github.com/epoberezkin/ajv-async) uses [nodent](https://github.com/MatAtBread/nodent) to transpile async functions. To use another transpiler you should separately install it (or load its bundle in the browser).
+
+
+#### Using nodent
+
+```javascript
+var ajv = new Ajv;
+require('ajv-async')(ajv);
+// in the browser if you want to load ajv-async bundle separately you can:
+// window.ajvAsync(ajv);
+var validate = ajv.compile(schema); // transpiled es7 async function
+validate(data).then(successFunc).catch(errorFunc);
+```
+
+
+#### Using other transpilers
+
+```javascript
+var ajv = new Ajv({ processCode: transpileFunc });
+var validate = ajv.compile(schema); // transpiled es7 async function
+validate(data).then(successFunc).catch(errorFunc);
+```
+
+See [Options](#options).
+
+
+## Security considerations
+
+JSON Schema, if properly used, can replace data sanitisation. It doesn't replace other API security considerations. It also introduces additional security aspects to consider.
+
+
+##### Untrusted schemas
+
+Ajv treats JSON schemas as trusted as your application code. This security model is based on the most common use case, when the schemas are static and bundled together with the application.
+
+If your schemas are received from untrusted sources (or generated from untrusted data) there are several scenarios you need to prevent:
+- compiling schemas can cause stack overflow (if they are too deep)
+- compiling schemas can be slow (e.g. [#557](https://github.com/epoberezkin/ajv/issues/557))
+- validating certain data can be slow
+
+It is difficult to predict all the scenarios, but at the very least it may help to limit the size of untrusted schemas (e.g. limit JSON string length) and also the maximum schema object depth (that can be high for relatively small JSON strings). You also may want to mitigate slow regular expressions in `pattern` and `patternProperties` keywords.
+
+Regardless the measures you take, using untrusted schemas increases security risks.
+
+
+##### Circular references in JavaScript objects
+
+Ajv does not support schemas and validated data that have circular references in objects. See [issue #802](https://github.com/epoberezkin/ajv/issues/802).
+
+An attempt to compile such schemas or validate such data would cause stack overflow (or will not complete in case of asynchronous validation). Depending on the parser you use, untrusted data can lead to circular references.
+
+
+##### Security risks of trusted schemas
+
+Some keywords in JSON Schemas can lead to very slow validation for certain data. These keywords include (but may be not limited to):
+
+- `pattern` and `format` for large strings - use `maxLength` to mitigate
+- `uniqueItems` for large non-scalar arrays - use `maxItems` to mitigate
+- `patternProperties` for large property names - use `propertyNames` to mitigate
+
+__Please note__: The suggestions above to prevent slow validation would only work if you do NOT use `allErrors: true` in production code (using it would continue validation after validation errors).
+
+You can validate your JSON schemas against [this meta-schema](https://github.com/epoberezkin/ajv/blob/master/lib/refs/json-schema-secure.json) to check that these recommendations are followed:
+
+```javascript
+const isSchemaSecure = ajv.compile(require('ajv/lib/refs/json-schema-secure.json'));
+
+const schema1 = {format: 'email'};
+isSchemaSecure(schema1); // false
+
+const schema2 = {format: 'email', maxLength: 256};
+isSchemaSecure(schema2); // true
+```
+
+__Please note__: following all these recommendation is not a guarantee that validation of untrusted data is safe - it can still lead to some undesirable results.
+
+
+## Filtering data
+
+With [option `removeAdditional`](#options) (added by [andyscott](https://github.com/andyscott)) you can filter data during the validation.
+
+This option modifies original data.
+
+Example:
+
+```javascript
+var ajv = new Ajv({ removeAdditional: true });
+var schema = {
+ "additionalProperties": false,
+ "properties": {
+ "foo": { "type": "number" },
+ "bar": {
+ "additionalProperties": { "type": "number" },
+ "properties": {
+ "baz": { "type": "string" }
+ }
+ }
+ }
+}
+
+var data = {
+ "foo": 0,
+ "additional1": 1, // will be removed; `additionalProperties` == false
+ "bar": {
+ "baz": "abc",
+ "additional2": 2 // will NOT be removed; `additionalProperties` != false
+ },
+}
+
+var validate = ajv.compile(schema);
+
+console.log(validate(data)); // true
+console.log(data); // { "foo": 0, "bar": { "baz": "abc", "additional2": 2 }
+```
+
+If `removeAdditional` option in the example above were `"all"` then both `additional1` and `additional2` properties would have been removed.
+
+If the option were `"failing"` then property `additional1` would have been removed regardless of its value and property `additional2` would have been removed only if its value were failing the schema in the inner `additionalProperties` (so in the example above it would have stayed because it passes the schema, but any non-number would have been removed).
+
+__Please note__: If you use `removeAdditional` option with `additionalProperties` keyword inside `anyOf`/`oneOf` keywords your validation can fail with this schema, for example:
+
+```json
+{
+ "type": "object",
+ "oneOf": [
+ {
+ "properties": {
+ "foo": { "type": "string" }
+ },
+ "required": [ "foo" ],
+ "additionalProperties": false
+ },
+ {
+ "properties": {
+ "bar": { "type": "integer" }
+ },
+ "required": [ "bar" ],
+ "additionalProperties": false
+ }
+ ]
+}
+```
+
+The intention of the schema above is to allow objects with either the string property "foo" or the integer property "bar", but not with both and not with any other properties.
+
+With the option `removeAdditional: true` the validation will pass for the object `{ "foo": "abc"}` but will fail for the object `{"bar": 1}`. It happens because while the first subschema in `oneOf` is validated, the property `bar` is removed because it is an additional property according to the standard (because it is not included in `properties` keyword in the same schema).
+
+While this behaviour is unexpected (issues [#129](https://github.com/epoberezkin/ajv/issues/129), [#134](https://github.com/epoberezkin/ajv/issues/134)), it is correct. To have the expected behaviour (both objects are allowed and additional properties are removed) the schema has to be refactored in this way:
+
+```json
+{
+ "type": "object",
+ "properties": {
+ "foo": { "type": "string" },
+ "bar": { "type": "integer" }
+ },
+ "additionalProperties": false,
+ "oneOf": [
+ { "required": [ "foo" ] },
+ { "required": [ "bar" ] }
+ ]
+}
+```
+
+The schema above is also more efficient - it will compile into a faster function.
+
+
+## Assigning defaults
+
+With [option `useDefaults`](#options) Ajv will assign values from `default` keyword in the schemas of `properties` and `items` (when it is the array of schemas) to the missing properties and items.
+
+With the option value `"empty"` properties and items equal to `null` or `""` (empty string) will be considered missing and assigned defaults.
+
+This option modifies original data.
+
+__Please note__: the default value is inserted in the generated validation code as a literal, so the value inserted in the data will be the deep clone of the default in the schema.
+
+
+Example 1 (`default` in `properties`):
+
+```javascript
+var ajv = new Ajv({ useDefaults: true });
+var schema = {
+ "type": "object",
+ "properties": {
+ "foo": { "type": "number" },
+ "bar": { "type": "string", "default": "baz" }
+ },
+ "required": [ "foo", "bar" ]
+};
+
+var data = { "foo": 1 };
+
+var validate = ajv.compile(schema);
+
+console.log(validate(data)); // true
+console.log(data); // { "foo": 1, "bar": "baz" }
+```
+
+Example 2 (`default` in `items`):
+
+```javascript
+var schema = {
+ "type": "array",
+ "items": [
+ { "type": "number" },
+ { "type": "string", "default": "foo" }
+ ]
+}
+
+var data = [ 1 ];
+
+var validate = ajv.compile(schema);
+
+console.log(validate(data)); // true
+console.log(data); // [ 1, "foo" ]
+```
+
+`default` keywords in other cases are ignored:
+
+- not in `properties` or `items` subschemas
+- in schemas inside `anyOf`, `oneOf` and `not` (see [#42](https://github.com/epoberezkin/ajv/issues/42))
+- in `if` subschema of `switch` keyword
+- in schemas generated by custom macro keywords
+
+The [`strictDefaults` option](#options) customizes Ajv's behavior for the defaults that Ajv ignores (`true` raises an error, and `"log"` outputs a warning).
+
+
+## Coercing data types
+
+When you are validating user inputs all your data properties are usually strings. The option `coerceTypes` allows you to have your data types coerced to the types specified in your schema `type` keywords, both to pass the validation and to use the correctly typed data afterwards.
+
+This option modifies original data.
+
+__Please note__: if you pass a scalar value to the validating function its type will be coerced and it will pass the validation, but the value of the variable you pass won't be updated because scalars are passed by value.
+
+
+Example 1:
+
+```javascript
+var ajv = new Ajv({ coerceTypes: true });
+var schema = {
+ "type": "object",
+ "properties": {
+ "foo": { "type": "number" },
+ "bar": { "type": "boolean" }
+ },
+ "required": [ "foo", "bar" ]
+};
+
+var data = { "foo": "1", "bar": "false" };
+
+var validate = ajv.compile(schema);
+
+console.log(validate(data)); // true
+console.log(data); // { "foo": 1, "bar": false }
+```
+
+Example 2 (array coercions):
+
+```javascript
+var ajv = new Ajv({ coerceTypes: 'array' });
+var schema = {
+ "properties": {
+ "foo": { "type": "array", "items": { "type": "number" } },
+ "bar": { "type": "boolean" }
+ }
+};
+
+var data = { "foo": "1", "bar": ["false"] };
+
+var validate = ajv.compile(schema);
+
+console.log(validate(data)); // true
+console.log(data); // { "foo": [1], "bar": false }
+```
+
+The coercion rules, as you can see from the example, are different from JavaScript both to validate user input as expected and to have the coercion reversible (to correctly validate cases where different types are defined in subschemas of "anyOf" and other compound keywords).
+
+See [Coercion rules](https://github.com/epoberezkin/ajv/blob/master/COERCION.md) for details.
+
+
+## API
+
+##### new Ajv(Object options) -> Object
+
+Create Ajv instance.
+
+
+##### .compile(Object schema) -> Function<Object data>
+
+Generate validating function and cache the compiled schema for future use.
+
+Validating function returns a boolean value. This function has properties `errors` and `schema`. Errors encountered during the last validation are assigned to `errors` property (it is assigned `null` if there was no errors). `schema` property contains the reference to the original schema.
+
+The schema passed to this method will be validated against meta-schema unless `validateSchema` option is false. If schema is invalid, an error will be thrown. See [options](#options).
+
+
+##### .compileAsync(Object schema [, Boolean meta] [, Function callback]) -> Promise
+
+Asynchronous version of `compile` method that loads missing remote schemas using asynchronous function in `options.loadSchema`. This function returns a Promise that resolves to a validation function. An optional callback passed to `compileAsync` will be called with 2 parameters: error (or null) and validating function. The returned promise will reject (and the callback will be called with an error) when:
+
+- missing schema can't be loaded (`loadSchema` returns a Promise that rejects).
+- a schema containing a missing reference is loaded, but the reference cannot be resolved.
+- schema (or some loaded/referenced schema) is invalid.
+
+The function compiles schema and loads the first missing schema (or meta-schema) until all missing schemas are loaded.
+
+You can asynchronously compile meta-schema by passing `true` as the second parameter.
+
+See example in [Asynchronous compilation](#asynchronous-schema-compilation).
+
+
+##### .validate(Object schema|String key|String ref, data) -> Boolean
+
+Validate data using passed schema (it will be compiled and cached).
+
+Instead of the schema you can use the key that was previously passed to `addSchema`, the schema id if it was present in the schema or any previously resolved reference.
+
+Validation errors will be available in the `errors` property of Ajv instance (`null` if there were no errors).
+
+__Please note__: every time this method is called the errors are overwritten so you need to copy them to another variable if you want to use them later.
+
+If the schema is asynchronous (has `$async` keyword on the top level) this method returns a Promise. See [Asynchronous validation](#asynchronous-validation).
+
+
+##### .addSchema(Array<Object>|Object schema [, String key]) -> Ajv
+
+Add schema(s) to validator instance. This method does not compile schemas (but it still validates them). Because of that dependencies can be added in any order and circular dependencies are supported. It also prevents unnecessary compilation of schemas that are containers for other schemas but not used as a whole.
+
+Array of schemas can be passed (schemas should have ids), the second parameter will be ignored.
+
+Key can be passed that can be used to reference the schema and will be used as the schema id if there is no id inside the schema. If the key is not passed, the schema id will be used as the key.
+
+
+Once the schema is added, it (and all the references inside it) can be referenced in other schemas and used to validate data.
+
+Although `addSchema` does not compile schemas, explicit compilation is not required - the schema will be compiled when it is used first time.
+
+By default the schema is validated against meta-schema before it is added, and if the schema does not pass validation the exception is thrown. This behaviour is controlled by `validateSchema` option.
+
+__Please note__: Ajv uses the [method chaining syntax](https://en.wikipedia.org/wiki/Method_chaining) for all methods with the prefix `add*` and `remove*`.
+This allows you to do nice things like the following.
+
+```javascript
+var validate = new Ajv().addSchema(schema).addFormat(name, regex).getSchema(uri);
+```
+
+##### .addMetaSchema(Array<Object>|Object schema [, String key]) -> Ajv
+
+Adds meta schema(s) that can be used to validate other schemas. That function should be used instead of `addSchema` because there may be instance options that would compile a meta schema incorrectly (at the moment it is `removeAdditional` option).
+
+There is no need to explicitly add draft-07 meta schema (http://json-schema.org/draft-07/schema) - it is added by default, unless option `meta` is set to `false`. You only need to use it if you have a changed meta-schema that you want to use to validate your schemas. See `validateSchema`.
+
+
+##### .validateSchema(Object schema) -> Boolean
+
+Validates schema. This method should be used to validate schemas rather than `validate` due to the inconsistency of `uri` format in JSON Schema standard.
+
+By default this method is called automatically when the schema is added, so you rarely need to use it directly.
+
+If schema doesn't have `$schema` property, it is validated against draft 6 meta-schema (option `meta` should not be false).
+
+If schema has `$schema` property, then the schema with this id (that should be previously added) is used to validate passed schema.
+
+Errors will be available at `ajv.errors`.
+
+
+##### .getSchema(String key) -> Function<Object data>
+
+Retrieve compiled schema previously added with `addSchema` by the key passed to `addSchema` or by its full reference (id). The returned validating function has `schema` property with the reference to the original schema.
+
+
+##### .removeSchema([Object schema|String key|String ref|RegExp pattern]) -> Ajv
+
+Remove added/cached schema. Even if schema is referenced by other schemas it can be safely removed as dependent schemas have local references.
+
+Schema can be removed using:
+- key passed to `addSchema`
+- it's full reference (id)
+- RegExp that should match schema id or key (meta-schemas won't be removed)
+- actual schema object that will be stable-stringified to remove schema from cache
+
+If no parameter is passed all schemas but meta-schemas will be removed and the cache will be cleared.
+
+
+##### .addFormat(String name, String|RegExp|Function|Object format) -> Ajv
+
+Add custom format to validate strings or numbers. It can also be used to replace pre-defined formats for Ajv instance.
+
+Strings are converted to RegExp.
+
+Function should return validation result as `true` or `false`.
+
+If object is passed it should have properties `validate`, `compare` and `async`:
+
+- _validate_: a string, RegExp or a function as described above.
+- _compare_: an optional comparison function that accepts two strings and compares them according to the format meaning. This function is used with keywords `formatMaximum`/`formatMinimum` (defined in [ajv-keywords](https://github.com/epoberezkin/ajv-keywords) package). It should return `1` if the first value is bigger than the second value, `-1` if it is smaller and `0` if it is equal.
+- _async_: an optional `true` value if `validate` is an asynchronous function; in this case it should return a promise that resolves with a value `true` or `false`.
+- _type_: an optional type of data that the format applies to. It can be `"string"` (default) or `"number"` (see https://github.com/epoberezkin/ajv/issues/291#issuecomment-259923858). If the type of data is different, the validation will pass.
+
+Custom formats can be also added via `formats` option.
+
+
+##### .addKeyword(String keyword, Object definition) -> Ajv
+
+Add custom validation keyword to Ajv instance.
+
+Keyword should be different from all standard JSON Schema keywords and different from previously defined keywords. There is no way to redefine keywords or to remove keyword definition from the instance.
+
+Keyword must start with a letter, `_` or `$`, and may continue with letters, numbers, `_`, `$`, or `-`.
+It is recommended to use an application-specific prefix for keywords to avoid current and future name collisions.
+
+Example Keywords:
+- `"xyz-example"`: valid, and uses prefix for the xyz project to avoid name collisions.
+- `"example"`: valid, but not recommended as it could collide with future versions of JSON Schema etc.
+- `"3-example"`: invalid as numbers are not allowed to be the first character in a keyword
+
+Keyword definition is an object with the following properties:
+
+- _type_: optional string or array of strings with data type(s) that the keyword applies to. If not present, the keyword will apply to all types.
+- _validate_: validating function
+- _compile_: compiling function
+- _macro_: macro function
+- _inline_: compiling function that returns code (as string)
+- _schema_: an optional `false` value used with "validate" keyword to not pass schema
+- _metaSchema_: an optional meta-schema for keyword schema
+- _dependencies_: an optional list of properties that must be present in the parent schema - it will be checked during schema compilation
+- _modifying_: `true` MUST be passed if keyword modifies data
+- _statements_: `true` can be passed in case inline keyword generates statements (as opposed to expression)
+- _valid_: pass `true`/`false` to pre-define validation result, the result returned from validation function will be ignored. This option cannot be used with macro keywords.
+- _$data_: an optional `true` value to support [$data reference](#data-reference) as the value of custom keyword. The reference will be resolved at validation time. If the keyword has meta-schema it would be extended to allow $data and it will be used to validate the resolved value. Supporting $data reference requires that keyword has validating function (as the only option or in addition to compile, macro or inline function).
+- _async_: an optional `true` value if the validation function is asynchronous (whether it is compiled or passed in _validate_ property); in this case it should return a promise that resolves with a value `true` or `false`. This option is ignored in case of "macro" and "inline" keywords.
+- _errors_: an optional boolean or string `"full"` indicating whether keyword returns errors. If this property is not set Ajv will determine if the errors were set in case of failed validation.
+
+_compile_, _macro_ and _inline_ are mutually exclusive, only one should be used at a time. _validate_ can be used separately or in addition to them to support $data reference.
+
+__Please note__: If the keyword is validating data type that is different from the type(s) in its definition, the validation function will not be called (and expanded macro will not be used), so there is no need to check for data type inside validation function or inside schema returned by macro function (unless you want to enforce a specific type and for some reason do not want to use a separate `type` keyword for that). In the same way as standard keywords work, if the keyword does not apply to the data type being validated, the validation of this keyword will succeed.
+
+See [Defining custom keywords](#defining-custom-keywords) for more details.
+
+
+##### .getKeyword(String keyword) -> Object|Boolean
+
+Returns custom keyword definition, `true` for pre-defined keywords and `false` if the keyword is unknown.
+
+
+##### .removeKeyword(String keyword) -> Ajv
+
+Removes custom or pre-defined keyword so you can redefine them.
+
+While this method can be used to extend pre-defined keywords, it can also be used to completely change their meaning - it may lead to unexpected results.
+
+__Please note__: schemas compiled before the keyword is removed will continue to work without changes. To recompile schemas use `removeSchema` method and compile them again.
+
+
+##### .errorsText([Array<Object> errors [, Object options]]) -> String
+
+Returns the text with all errors in a String.
+
+Options can have properties `separator` (string used to separate errors, ", " by default) and `dataVar` (the variable name that dataPaths are prefixed with, "data" by default).
+
+
+## Options
+
+Defaults:
+
+```javascript
+{
+ // validation and reporting options:
+ $data: false,
+ allErrors: false,
+ verbose: false,
+ $comment: false, // NEW in Ajv version 6.0
+ jsonPointers: false,
+ uniqueItems: true,
+ unicode: true,
+ nullable: false,
+ format: 'fast',
+ formats: {},
+ unknownFormats: true,
+ schemas: {},
+ logger: undefined,
+ // referenced schema options:
+ schemaId: '$id',
+ missingRefs: true,
+ extendRefs: 'ignore', // recommended 'fail'
+ loadSchema: undefined, // function(uri: string): Promise {}
+ // options to modify validated data:
+ removeAdditional: false,
+ useDefaults: false,
+ coerceTypes: false,
+ // strict mode options
+ strictDefaults: false,
+ strictKeywords: false,
+ // asynchronous validation options:
+ transpile: undefined, // requires ajv-async package
+ // advanced options:
+ meta: true,
+ validateSchema: true,
+ addUsedSchema: true,
+ inlineRefs: true,
+ passContext: false,
+ loopRequired: Infinity,
+ ownProperties: false,
+ multipleOfPrecision: false,
+ errorDataPath: 'object', // deprecated
+ messages: true,
+ sourceCode: false,
+ processCode: undefined, // function (str: string): string {}
+ cache: new Cache,
+ serialize: undefined
+}
+```
+
+##### Validation and reporting options
+
+- _$data_: support [$data references](#data-reference). Draft 6 meta-schema that is added by default will be extended to allow them. If you want to use another meta-schema you need to use $dataMetaSchema method to add support for $data reference. See [API](#api).
+- _allErrors_: check all rules collecting all errors. Default is to return after the first error.
+- _verbose_: include the reference to the part of the schema (`schema` and `parentSchema`) and validated data in errors (false by default).
+- _$comment_ (NEW in Ajv version 6.0): log or pass the value of `$comment` keyword to a function. Option values:
+ - `false` (default): ignore $comment keyword.
+ - `true`: log the keyword value to console.
+ - function: pass the keyword value, its schema path and root schema to the specified function
+- _jsonPointers_: set `dataPath` property of errors using [JSON Pointers](https://tools.ietf.org/html/rfc6901) instead of JavaScript property access notation.
+- _uniqueItems_: validate `uniqueItems` keyword (true by default).
+- _unicode_: calculate correct length of strings with unicode pairs (true by default). Pass `false` to use `.length` of strings that is faster, but gives "incorrect" lengths of strings with unicode pairs - each unicode pair is counted as two characters.
+- _nullable_: support keyword "nullable" from [Open API 3 specification](https://swagger.io/docs/specification/data-models/data-types/).
+- _format_: formats validation mode. Option values:
+ - `"fast"` (default) - simplified and fast validation (see [Formats](#formats) for details of which formats are available and affected by this option).
+ - `"full"` - more restrictive and slow validation. E.g., 25:00:00 and 2015/14/33 will be invalid time and date in 'full' mode but it will be valid in 'fast' mode.
+ - `false` - ignore all format keywords.
+- _formats_: an object with custom formats. Keys and values will be passed to `addFormat` method.
+- _unknownFormats_: handling of unknown formats. Option values:
+ - `true` (default) - if an unknown format is encountered the exception is thrown during schema compilation. If `format` keyword value is [$data reference](#data-reference) and it is unknown the validation will fail.
+ - `[String]` - an array of unknown format names that will be ignored. This option can be used to allow usage of third party schemas with format(s) for which you don't have definitions, but still fail if another unknown format is used. If `format` keyword value is [$data reference](#data-reference) and it is not in this array the validation will fail.
+ - `"ignore"` - to log warning during schema compilation and always pass validation (the default behaviour in versions before 5.0.0). This option is not recommended, as it allows to mistype format name and it won't be validated without any error message. This behaviour is required by JSON Schema specification.
+- _schemas_: an array or object of schemas that will be added to the instance. In case you pass the array the schemas must have IDs in them. When the object is passed the method `addSchema(value, key)` will be called for each schema in this object.
+- _logger_: sets the logging method. Default is the global `console` object that should have methods `log`, `warn` and `error`. Option values:
+ - custom logger - it should have methods `log`, `warn` and `error`. If any of these methods is missing an exception will be thrown.
+ - `false` - logging is disabled.
+
+
+##### Referenced schema options
+
+- _schemaId_: this option defines which keywords are used as schema URI. Option value:
+ - `"$id"` (default) - only use `$id` keyword as schema URI (as specified in JSON Schema draft-06/07), ignore `id` keyword (if it is present a warning will be logged).
+ - `"id"` - only use `id` keyword as schema URI (as specified in JSON Schema draft-04), ignore `$id` keyword (if it is present a warning will be logged).
+ - `"auto"` - use both `$id` and `id` keywords as schema URI. If both are present (in the same schema object) and different the exception will be thrown during schema compilation.
+- _missingRefs_: handling of missing referenced schemas. Option values:
+ - `true` (default) - if the reference cannot be resolved during compilation the exception is thrown. The thrown error has properties `missingRef` (with hash fragment) and `missingSchema` (without it). Both properties are resolved relative to the current base id (usually schema id, unless it was substituted).
+ - `"ignore"` - to log error during compilation and always pass validation.
+ - `"fail"` - to log error and successfully compile schema but fail validation if this rule is checked.
+- _extendRefs_: validation of other keywords when `$ref` is present in the schema. Option values:
+ - `"ignore"` (default) - when `$ref` is used other keywords are ignored (as per [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03#section-3) standard). A warning will be logged during the schema compilation.
+ - `"fail"` (recommended) - if other validation keywords are used together with `$ref` the exception will be thrown when the schema is compiled. This option is recommended to make sure schema has no keywords that are ignored, which can be confusing.
+ - `true` - validate all keywords in the schemas with `$ref` (the default behaviour in versions before 5.0.0).
+- _loadSchema_: asynchronous function that will be used to load remote schemas when `compileAsync` [method](#api-compileAsync) is used and some reference is missing (option `missingRefs` should NOT be 'fail' or 'ignore'). This function should accept remote schema uri as a parameter and return a Promise that resolves to a schema. See example in [Asynchronous compilation](#asynchronous-schema-compilation).
+
+
+##### Options to modify validated data
+
+- _removeAdditional_: remove additional properties - see example in [Filtering data](#filtering-data). This option is not used if schema is added with `addMetaSchema` method. Option values:
+ - `false` (default) - not to remove additional properties
+ - `"all"` - all additional properties are removed, regardless of `additionalProperties` keyword in schema (and no validation is made for them).
+ - `true` - only additional properties with `additionalProperties` keyword equal to `false` are removed.
+ - `"failing"` - additional properties that fail schema validation will be removed (where `additionalProperties` keyword is `false` or schema).
+- _useDefaults_: replace missing or undefined properties and items with the values from corresponding `default` keywords. Default behaviour is to ignore `default` keywords. This option is not used if schema is added with `addMetaSchema` method. See examples in [Assigning defaults](#assigning-defaults). Option values:
+ - `false` (default) - do not use defaults
+ - `true` - insert defaults by value (object literal is used).
+ - `"empty"` - in addition to missing or undefined, use defaults for properties and items that are equal to `null` or `""` (an empty string).
+ - `"shared"` (deprecated) - insert defaults by reference. If the default is an object, it will be shared by all instances of validated data. If you modify the inserted default in the validated data, it will be modified in the schema as well.
+- _coerceTypes_: change data type of data to match `type` keyword. See the example in [Coercing data types](#coercing-data-types) and [coercion rules](https://github.com/epoberezkin/ajv/blob/master/COERCION.md). Option values:
+ - `false` (default) - no type coercion.
+ - `true` - coerce scalar data types.
+ - `"array"` - in addition to coercions between scalar types, coerce scalar data to an array with one element and vice versa (as required by the schema).
+
+
+##### Strict mode options
+
+- _strictDefaults_: report ignored `default` keywords in schemas. Option values:
+ - `false` (default) - ignored defaults are not reported
+ - `true` - if an ignored default is present, throw an error
+ - `"log"` - if an ignored default is present, log warning
+- _strictKeywords_: report unknown keywords in schemas. Option values:
+ - `false` (default) - unknown keywords are not reported
+ - `true` - if an unknown keyword is present, throw an error
+ - `"log"` - if an unknown keyword is present, log warning
+
+
+##### Asynchronous validation options
+
+- _transpile_: Requires [ajv-async](https://github.com/epoberezkin/ajv-async) package. It determines whether Ajv transpiles compiled asynchronous validation function. Option values:
+ - `undefined` (default) - transpile with [nodent](https://github.com/MatAtBread/nodent) if async functions are not supported.
+ - `true` - always transpile with nodent.
+ - `false` - do not transpile; if async functions are not supported an exception will be thrown.
+
+
+##### Advanced options
+
+- _meta_: add [meta-schema](http://json-schema.org/documentation.html) so it can be used by other schemas (true by default). If an object is passed, it will be used as the default meta-schema for schemas that have no `$schema` keyword. This default meta-schema MUST have `$schema` keyword.
+- _validateSchema_: validate added/compiled schemas against meta-schema (true by default). `$schema` property in the schema can be http://json-schema.org/draft-07/schema or absent (draft-07 meta-schema will be used) or can be a reference to the schema previously added with `addMetaSchema` method. Option values:
+ - `true` (default) - if the validation fails, throw the exception.
+ - `"log"` - if the validation fails, log error.
+ - `false` - skip schema validation.
+- _addUsedSchema_: by default methods `compile` and `validate` add schemas to the instance if they have `$id` (or `id`) property that doesn't start with "#". If `$id` is present and it is not unique the exception will be thrown. Set this option to `false` to skip adding schemas to the instance and the `$id` uniqueness check when these methods are used. This option does not affect `addSchema` method.
+- _inlineRefs_: Affects compilation of referenced schemas. Option values:
+ - `true` (default) - the referenced schemas that don't have refs in them are inlined, regardless of their size - that substantially improves performance at the cost of the bigger size of compiled schema functions.
+ - `false` - to not inline referenced schemas (they will be compiled as separate functions).
+ - integer number - to limit the maximum number of keywords of the schema that will be inlined.
+- _passContext_: pass validation context to custom keyword functions. If this option is `true` and you pass some context to the compiled validation function with `validate.call(context, data)`, the `context` will be available as `this` in your custom keywords. By default `this` is Ajv instance.
+- _loopRequired_: by default `required` keyword is compiled into a single expression (or a sequence of statements in `allErrors` mode). In case of a very large number of properties in this keyword it may result in a very big validation function. Pass integer to set the number of properties above which `required` keyword will be validated in a loop - smaller validation function size but also worse performance.
+- _ownProperties_: by default Ajv iterates over all enumerable object properties; when this option is `true` only own enumerable object properties (i.e. found directly on the object rather than on its prototype) are iterated. Contributed by @mbroadst.
+- _multipleOfPrecision_: by default `multipleOf` keyword is validated by comparing the result of division with parseInt() of that result. It works for dividers that are bigger than 1. For small dividers such as 0.01 the result of the division is usually not integer (even when it should be integer, see issue [#84](https://github.com/epoberezkin/ajv/issues/84)). If you need to use fractional dividers set this option to some positive integer N to have `multipleOf` validated using this formula: `Math.abs(Math.round(division) - division) < 1e-N` (it is slower but allows for float arithmetics deviations).
+- _errorDataPath_ (deprecated): set `dataPath` to point to 'object' (default) or to 'property' when validating keywords `required`, `additionalProperties` and `dependencies`.
+- _messages_: Include human-readable messages in errors. `true` by default. `false` can be passed when custom messages are used (e.g. with [ajv-i18n](https://github.com/epoberezkin/ajv-i18n)).
+- _sourceCode_: add `sourceCode` property to validating function (for debugging; this code can be different from the result of toString call).
+- _processCode_: an optional function to process generated code before it is passed to Function constructor. It can be used to either beautify (the validating function is generated without line-breaks) or to transpile code. Starting from version 5.0.0 this option replaced options:
+ - `beautify` that formatted the generated function using [js-beautify](https://github.com/beautify-web/js-beautify). If you want to beautify the generated code pass `require('js-beautify').js_beautify`.
+ - `transpile` that transpiled asynchronous validation function. You can still use `transpile` option with [ajv-async](https://github.com/epoberezkin/ajv-async) package. See [Asynchronous validation](#asynchronous-validation) for more information.
+- _cache_: an optional instance of cache to store compiled schemas using stable-stringified schema as a key. For example, set-associative cache [sacjs](https://github.com/epoberezkin/sacjs) can be used. If not passed then a simple hash is used which is good enough for the common use case (a limited number of statically defined schemas). Cache should have methods `put(key, value)`, `get(key)`, `del(key)` and `clear()`.
+- _serialize_: an optional function to serialize schema to cache key. Pass `false` to use schema itself as a key (e.g., if WeakMap used as a cache). By default [fast-json-stable-stringify](https://github.com/epoberezkin/fast-json-stable-stringify) is used.
+
+
+## Validation errors
+
+In case of validation failure, Ajv assigns the array of errors to `errors` property of validation function (or to `errors` property of Ajv instance when `validate` or `validateSchema` methods were called). In case of [asynchronous validation](#asynchronous-validation), the returned promise is rejected with exception `Ajv.ValidationError` that has `errors` property.
+
+
+### Error objects
+
+Each error is an object with the following properties:
+
+- _keyword_: validation keyword.
+- _dataPath_: the path to the part of the data that was validated. By default `dataPath` uses JavaScript property access notation (e.g., `".prop[1].subProp"`). When the option `jsonPointers` is true (see [Options](#options)) `dataPath` will be set using JSON pointer standard (e.g., `"/prop/1/subProp"`).
+- _schemaPath_: the path (JSON-pointer as a URI fragment) to the schema of the keyword that failed validation.
+- _params_: the object with the additional information about error that can be used to create custom error messages (e.g., using [ajv-i18n](https://github.com/epoberezkin/ajv-i18n) package). See below for parameters set by all keywords.
+- _message_: the standard error message (can be excluded with option `messages` set to false).
+- _schema_: the schema of the keyword (added with `verbose` option).
+- _parentSchema_: the schema containing the keyword (added with `verbose` option)
+- _data_: the data validated by the keyword (added with `verbose` option).
+
+__Please note__: `propertyNames` keyword schema validation errors have an additional property `propertyName`, `dataPath` points to the object. After schema validation for each property name, if it is invalid an additional error is added with the property `keyword` equal to `"propertyNames"`.
+
+
+### Error parameters
+
+Properties of `params` object in errors depend on the keyword that failed validation.
+
+- `maxItems`, `minItems`, `maxLength`, `minLength`, `maxProperties`, `minProperties` - property `limit` (number, the schema of the keyword).
+- `additionalItems` - property `limit` (the maximum number of allowed items in case when `items` keyword is an array of schemas and `additionalItems` is false).
+- `additionalProperties` - property `additionalProperty` (the property not used in `properties` and `patternProperties` keywords).
+- `dependencies` - properties:
+ - `property` (dependent property),
+ - `missingProperty` (required missing dependency - only the first one is reported currently)
+ - `deps` (required dependencies, comma separated list as a string),
+ - `depsCount` (the number of required dependencies).
+- `format` - property `format` (the schema of the keyword).
+- `maximum`, `minimum` - properties:
+ - `limit` (number, the schema of the keyword),
+ - `exclusive` (boolean, the schema of `exclusiveMaximum` or `exclusiveMinimum`),
+ - `comparison` (string, comparison operation to compare the data to the limit, with the data on the left and the limit on the right; can be "<", "<=", ">", ">=")
+- `multipleOf` - property `multipleOf` (the schema of the keyword)
+- `pattern` - property `pattern` (the schema of the keyword)
+- `required` - property `missingProperty` (required property that is missing).
+- `propertyNames` - property `propertyName` (an invalid property name).
+- `patternRequired` (in ajv-keywords) - property `missingPattern` (required pattern that did not match any property).
+- `type` - property `type` (required type(s), a string, can be a comma-separated list)
+- `uniqueItems` - properties `i` and `j` (indices of duplicate items).
+- `const` - property `allowedValue` pointing to the value (the schema of the keyword).
+- `enum` - property `allowedValues` pointing to the array of values (the schema of the keyword).
+- `$ref` - property `ref` with the referenced schema URI.
+- `oneOf` - property `passingSchemas` (array of indices of passing schemas, null if no schema passes).
+- custom keywords (in case keyword definition doesn't create errors) - property `keyword` (the keyword name).
+
+
+## Plugins
+
+Ajv can be extended with plugins that add custom keywords, formats or functions to process generated code. When such plugin is published as npm package it is recommended that it follows these conventions:
+
+- it exports a function
+- this function accepts ajv instance as the first parameter and returns the same instance to allow chaining
+- this function can accept an optional configuration as the second parameter
+
+If you have published a useful plugin please submit a PR to add it to the next section.
+
+
+## Related packages
+
+- [ajv-async](https://github.com/epoberezkin/ajv-async) - plugin to configure async validation mode
+- [ajv-bsontype](https://github.com/BoLaMN/ajv-bsontype) - plugin to validate mongodb's bsonType formats
+- [ajv-cli](https://github.com/jessedc/ajv-cli) - command line interface
+- [ajv-errors](https://github.com/epoberezkin/ajv-errors) - plugin for custom error messages
+- [ajv-i18n](https://github.com/epoberezkin/ajv-i18n) - internationalised error messages
+- [ajv-istanbul](https://github.com/epoberezkin/ajv-istanbul) - plugin to instrument generated validation code to measure test coverage of your schemas
+- [ajv-keywords](https://github.com/epoberezkin/ajv-keywords) - plugin with custom validation keywords (select, typeof, etc.)
+- [ajv-merge-patch](https://github.com/epoberezkin/ajv-merge-patch) - plugin with keywords $merge and $patch
+- [ajv-pack](https://github.com/epoberezkin/ajv-pack) - produces a compact module exporting validation functions
+
+
+## Some packages using Ajv
+
+- [webpack](https://github.com/webpack/webpack) - a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser
+- [jsonscript-js](https://github.com/JSONScript/jsonscript-js) - the interpreter for [JSONScript](http://www.jsonscript.org) - scripted processing of existing endpoints and services
+- [osprey-method-handler](https://github.com/mulesoft-labs/osprey-method-handler) - Express middleware for validating requests and responses based on a RAML method object, used in [osprey](https://github.com/mulesoft/osprey) - validating API proxy generated from a RAML definition
+- [har-validator](https://github.com/ahmadnassri/har-validator) - HTTP Archive (HAR) validator
+- [jsoneditor](https://github.com/josdejong/jsoneditor) - a web-based tool to view, edit, format, and validate JSON http://jsoneditoronline.org
+- [JSON Schema Lint](https://github.com/nickcmaynard/jsonschemalint) - a web tool to validate JSON/YAML document against a single JSON Schema http://jsonschemalint.com
+- [objection](https://github.com/vincit/objection.js) - SQL-friendly ORM for Node.js
+- [table](https://github.com/gajus/table) - formats data into a string table
+- [ripple-lib](https://github.com/ripple/ripple-lib) - a JavaScript API for interacting with [Ripple](https://ripple.com) in Node.js and the browser
+- [restbase](https://github.com/wikimedia/restbase) - distributed storage with REST API & dispatcher for backend services built to provide a low-latency & high-throughput API for Wikipedia / Wikimedia content
+- [hippie-swagger](https://github.com/CacheControl/hippie-swagger) - [Hippie](https://github.com/vesln/hippie) wrapper that provides end to end API testing with swagger validation
+- [react-form-controlled](https://github.com/seeden/react-form-controlled) - React controlled form components with validation
+- [rabbitmq-schema](https://github.com/tjmehta/rabbitmq-schema) - a schema definition module for RabbitMQ graphs and messages
+- [@query/schema](https://www.npmjs.com/package/@query/schema) - stream filtering with a URI-safe query syntax parsing to JSON Schema
+- [chai-ajv-json-schema](https://github.com/peon374/chai-ajv-json-schema) - chai plugin to us JSON Schema with expect in mocha tests
+- [grunt-jsonschema-ajv](https://github.com/SignpostMarv/grunt-jsonschema-ajv) - Grunt plugin for validating files against JSON Schema
+- [extract-text-webpack-plugin](https://github.com/webpack-contrib/extract-text-webpack-plugin) - extract text from bundle into a file
+- [electron-builder](https://github.com/electron-userland/electron-builder) - a solution to package and build a ready for distribution Electron app
+- [addons-linter](https://github.com/mozilla/addons-linter) - Mozilla Add-ons Linter
+- [gh-pages-generator](https://github.com/epoberezkin/gh-pages-generator) - multi-page site generator converting markdown files to GitHub pages
+- [ESLint](https://github.com/eslint/eslint) - the pluggable linting utility for JavaScript and JSX
+
+
+## Tests
+
+```
+npm install
+git submodule update --init
+npm test
+```
+
+## Contributing
+
+All validation functions are generated using doT templates in [dot](https://github.com/epoberezkin/ajv/tree/master/lib/dot) folder. Templates are precompiled so doT is not a run-time dependency.
+
+`npm run build` - compiles templates to [dotjs](https://github.com/epoberezkin/ajv/tree/master/lib/dotjs) folder.
+
+`npm run watch` - automatically compiles templates when files in dot folder change
+
+Please see [Contributing guidelines](https://github.com/epoberezkin/ajv/blob/master/CONTRIBUTING.md)
+
+
+## Changes history
+
+See https://github.com/epoberezkin/ajv/releases
+
+__Please note__: [Changes in version 6.0.0](https://github.com/epoberezkin/ajv/releases/tag/v6.0.0).
+
+[Version 5.0.0](https://github.com/epoberezkin/ajv/releases/tag/5.0.0).
+
+[Version 4.0.0](https://github.com/epoberezkin/ajv/releases/tag/4.0.0).
+
+[Version 3.0.0](https://github.com/epoberezkin/ajv/releases/tag/3.0.0).
+
+[Version 2.0.0](https://github.com/epoberezkin/ajv/releases/tag/2.0.0).
+
+
+## License
+
+[MIT](https://github.com/epoberezkin/ajv/blob/master/LICENSE)
diff --git a/src/node_modules/ajv/dist/ajv.bundle.js b/src/node_modules/ajv/dist/ajv.bundle.js
new file mode 100644
index 0000000..286dc92
--- /dev/null
+++ b/src/node_modules/ajv/dist/ajv.bundle.js
@@ -0,0 +1,7165 @@
+(function(f){if(typeof exports==="object"&&typeof module!=="undefined"){module.exports=f()}else if(typeof define==="function"&&define.amd){define([],f)}else{var g;if(typeof window!=="undefined"){g=window}else if(typeof global!=="undefined"){g=global}else if(typeof self!=="undefined"){g=self}else{g=this}g.Ajv = f()}})(function(){var define,module,exports;return (function(){function r(e,n,t){function o(i,f){if(!n[i]){if(!e[i]){var c="function"==typeof require&&require;if(!f&&c)return c(i,!0);if(u)return u(i,!0);var a=new Error("Cannot find module '"+i+"'");throw a.code="MODULE_NOT_FOUND",a}var p=n[i]={exports:{}};e[i][0].call(p.exports,function(r){var n=e[i][1][r];return o(n||r)},p,p.exports,r,e,n,t)}return n[i].exports}for(var u="function"==typeof require&&require,i=0;i