다음을 통해 공유

Azure Storage Queue client library samples for JavaScript

  • Code Sample
Browse code

These sample programs show how to use the JavaScript client libraries for Azure Storage Queue in some common scenarios.

File Name Description
sharedKeyAuth.js authenticate using an account name and a static key
azureAdAuth.js authenticate with the storage service using Azure Active Directory
anonymousAuth.js authenticate anonymously using a SAS-encoded URL
connectionStringAuth.js authenticate with the storage service using a connection string
queueClient.js use QueueServiceClient to create a queue and send/receive/delete messages
listQueues.js list queues in the account, showing options for paging, resuming paging, etc.
proxyAuth.js configure proxy settings when connecting to the storage service
customPipeline.js use custom HTTP pipeline options when connecting to the service

Prerequisites

The sample programs are compatible with LTS versions of Node.js.

You need an Azure subscription and the following Azure resources to run these sample programs:

Samples retrieve credentials to access the service endpoint from environment variables. Alternatively, edit the source code to include the appropriate credentials. See each individual sample for details on which environment variables/credentials it requires to function.

Adapting the samples to run in the browser may require some additional consideration. For details, please see the package README.

Setup

To run the samples using the published version of the package:

  1. Install the dependencies using npm:
npm install

  1. Edit the file sample.env, adding the correct credentials to access the Azure service and run the samples. Then rename the file from sample.env to just .env. The sample programs will read this file automatically.

  2. Run whichever samples you like (note that some samples may require additional setup, see the table above):

node sharedKeyAuth.js

Alternatively, run a single sample with the correct environment variables set (setting up the .env file is not required if you do this), for example (cross-platform):

npx cross-env ACCOUNT_NAME="<account name>" ACCOUNT_KEY="<account key>" node sharedKeyAuth.js

Next Steps

Take a look at our API Documentation for more information about the APIs that are available in the clients.