TypeScript icon, indicating that this package has built-in type declarations

    10.3.0 • Public • Published

    Azure Storage SDK V10 for JavaScript - Queue


    This project provides a SDK in JavaScript that makes it easy to consume Microsoft Azure Storage services.

    Please note that this version of the SDK is a complete overhaul of the current Azure Storage SDK for Node.js and JavaScript in Browsers, and is based on the new Storage SDK architecture.


    • Queue Storage
      • Get/Set Queue Service Properties
      • Create/List/Delete Queues
      • Enqueue/Dequeue/Peek/Clear/Update/Delete Queue Messages
    • Features new
      • Asynchronous I/O for all operations using the async methods
      • HttpPipeline which enables a high degree of per-request configurability
      • 1-to-1 correlation with the Storage REST API for clarity and simplicity


    This SDK is compatible with Node.js and browsers, and validated against LTS Node.js versions (>=6.5) and latest versions of Chrome, Firefox and Edge.

    Compatible with IE11

    You need polyfills to make this library work with IE11. The easiest way is to use @babel/polyfill, or polyfill service. Or you can load separate polyfills for missed ES feature(s). This library depends on following ES features which need external polyfills loaded.

    • Promise
    • String.prototype.startsWith
    • String.prototype.endsWith
    • String.prototype.repeat
    • String.prototype.includes
    • Array.prototype.includes
    • Object.keys (Override IE11's Object.keys with ES6 polyfill forcely to enable ES6 behavior)

    Differences between Node.js and browsers

    There are differences between Node.js and browsers runtime. When getting start with this SDK, pay attention to APIs or classes marked with "ONLY AVAILABLE IN NODE.JS RUNTIME" or "ONLY AVAILABLE IN BROWSERS".

    Following features, interfaces, classes or functions are only available in Node.js
    • Shared Key Authorization based on account name and account key
      • SharedKeyCredential
    • Shared Access Signature(SAS) generation
      • generateAccountSASQueryParameters()
      • generateQueueSASQueryParameters()

    Getting Started


    The preferred way to install the Azure Storage SDK for JavaScript is to use the npm package manager. Simply type the following into a terminal window:

    npm install @azure/storage-queue

    In your TypeScript or JavaScript file, import via following:

    import * as Azure from "@azure/storage-queue";


    const Azure = require("@azure/storage-queue");

    JavaScript Bundle

    To use the SDK with JS bundle in the browsers, simply add a script tag to your HTML pages pointing to the downloaded JS bundle file(s):

    <script src="https://mydomain/azure-storage-queue.min.js"></script>

    The JS bundled file is compatible with UMD standard, if no module system found, following global variable(s) will be exported:

    • azqueue


    Download latest released JS bundles from links in the GitHub release page. Or from following links directly:


    You need to set up Cross-Origin Resource Sharing (CORS) rules for your storage account if you need to develop for browsers. Go to Azure portal and Azure Storage Explorer, find your storage account, create new CORS rules for blob/queue/file/table service(s).

    For example, you can create following CORS settings for debugging. But please customize the settings carefully according to your requirements in production environment.

    • Allowed origins: *
    • Allowed headers: *
    • Exposed headers: *
    • Maximum age (seconds): 86400

    SDK Architecture

    The Azure Storage SDK for JavaScript provides low-level and high-level APIs.

    • ServiceURL, QueueURL, MessagesURL and MessageIdURL objects provide the low-level API functionality and map one-to-one to the Azure Storage Queue REST APIs.

    Code Samples

    const {
    = require(".."); // Change to "@azure/storage-queue" in your package
    async function main() {
      // Enter your storage account name and shared key
      const account = "<account>";
      const accountKey = "<accountkey>";
      // Use SharedKeyCredential with storage account and account key
      const sharedKeyCredential = new SharedKeyCredential(account, accountKey);
      // Use TokenCredential with OAuth token
      const tokenCredential = new TokenCredential("token");
      tokenCredential.token = "renewedToken"; // Renew the token by updating token field of token credential
      // Use AnonymousCredential when url already includes a SAS signature
      const anonymousCredential = new AnonymousCredential();
      // Use sharedKeyCredential, tokenCredential or anonymousCredential to create a pipeline
      const pipeline = StorageURL.newPipeline(sharedKeyCredential, {
        // httpClient: MyHTTPClient, // A customized HTTP client implementing IHttpClient interface
        // logger: MyLogger, // A customized logger implementing IHttpPipelineLogger interface
        retryOptions: { maxTries: 4 }, // Retry options
        telemetry: { value: "BasicSample V10.0.0" } // Customized telemetry string
      // List queues
      const serviceURL = new ServiceURL(
        // When using AnonymousCredential, following url should include a valid SAS or support public access
      console.log(`List queues`);
      let marker;
      do {
        const listQueuesResponse = await serviceURL.listQueuesSegment(Aborter.none, marker);
        marker = listQueuesResponse.nextMarker;
        for (const queue of listQueuesResponse.queueItems) {
          console.log(`Queue: ${queue.name}`);
      } while (marker);
      // Create a new queue
      const queueName = `newqueue${new Date().getTime()}`;
      const queueURL = QueueURL.fromServiceURL(serviceURL, queueName);
      const createQueueResponse = await queueURL.create(Aborter.none);
        `Create queue ${queueName} successfully, service assigned request Id: ${createQueueResponse.requestId}`
      // Enqueue a message into the queue using the enqueue method.
      const messagesURL = MessagesURL.fromQueueURL(queueURL);
      const enqueueQueueResponse = await messagesURL.enqueue(Aborter.none, "Hello World!");
        `Enqueue message successfully, service assigned message Id: ${enqueueQueueResponse.messageId}, service assigned request Id: ${enqueueQueueResponse.requestId}`
      // Peek a message using peek method.
      const peekQueueResponse = await messagesURL.peek(Aborter.none);
      console.log(`The peeked message is: ${peekQueueResponse.peekedMessageItems[0].messageText}`);
      // You de-queue a message in two steps. Call GetMessage at which point the message becomes invisible to any other code reading messages
      // from this queue for a default period of 30 seconds. To finish removing the message from the queue, you call DeleteMessage.
      // This two-step process ensures that if your code fails to process a message due to hardware or software failure, another instance
      // of your code can get the same message and try again.
      const dequeueResponse = await messagesURL.dequeue(Aborter.none);
      if (dequeueResponse.dequeuedMessageItems.length == 1) {
        const dequeueMessageItem = dequeueResponse.dequeuedMessageItems[0];
        console.log(`Processing & deleting message with content: ${dequeueMessageItem.messageText}`);
        const messageIdURL = MessageIdURL.fromMessagesURL(messagesURL, dequeueMessageItem.messageId);
        const deleteMessageResponse = await messageIdURL.delete(
          `Delete message succesfully, service assigned request Id: ${deleteMessageResponse.requestId}`
      // Delete the queue.
      const deleteQueueResponse = await queueURL.delete(Aborter.none);
        `Delete queue successfully, service assigned request Id: ${deleteQueueResponse.requestId}`
    // An async method returns a Promise object, which is compatible with then().catch() coding style.
      .then(() => {
        console.log("Successfully executed sample.");
      .catch((err) => {

    More Code Samples


    This project is licensed under MIT.


    This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

    When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

    This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.


    npm i @azure/[email protected]





    Unpacked Size

    2.21 MB

    Total Files


    Last publish


    • avatar
    • avatar
    • avatar
    • avatar