The primary reason that we added `dev-tool run vendored` command is to manage dependencies centrally. Now we can achieve that with pnpm workspace/catalog feature. This PR removes most of the `dev-tool run vendored` usages from individual packages and replace them with direct tool calls. Those tools are also added to individual package's dev dependencies per Pnpm recommendation.
2.9 KiB
page_type, languages, products, urlFragment
| page_type | languages | products | urlFragment | ||
|---|---|---|---|---|---|
| sample |
|
|
developer-devcenter-javascript |
Azure DevCenter client library samples for JavaScript
These sample programs show how to use the JavaScript client libraries for Azure DevCenter in some common scenarios.
| File Name | Description |
|---|---|
| sampleCreateDevBox.js | Demonstrates creating, accessing, and deleting a Dev Box |
| sampleCreateEnvironment.js | Demonstrates creating, fetching outputs from, and deleting an Environment |
Prerequisites
The sample programs are compatible with LTS versions of Node.js.
You need an Azure subscription 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:
- Install the dependencies using
npm:
npm install
-
Edit the file
sample.env, adding the correct credentials to access the Azure service and run the samples. Then rename the file fromsample.envto just.env. The sample programs will read this file automatically. -
Run whichever samples you like (note that some samples may require additional setup, see the table above):
node sampleCreateDevBox.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):
cross-env DEVCENTER_ENDPOINT="<devcenter endpoint>" node sampleCreateDevBox.js
Next Steps
Take a look at our API Documentation for more information about the APIs that are available in the clients.