This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js.
Перейти к файлу
Azure SDK Bot 2d74a31931
Sync eng/common directory with azure-sdk-tools for PR 1335 (#13358)
* Lossen up $RELEASE_TITLE_REGEX to accomodate wrongly formated changelogs

* Update changelog logic to use ordered hashtable

* Update semver and Changelog logic

Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
2021-01-25 10:51:11 -08:00
.devcontainer Fix codespaces container creation (#13338) 2021-01-22 08:52:15 -08:00
.github add chradek to API codeowners list (#13303) 2021-01-20 14:19:35 -08:00
.scripts Regeneration and Other changes (#9711) 2020-06-25 22:11:17 -07:00
.vscode [Storage] azure-storage-file-datalake (#6337) 2019-12-05 10:58:26 +08:00
common Azure Quantum SDK for Azure SDK for JS (#13345) 2021-01-23 00:18:03 +00:00
documentation [Identity] More standard samples (#12800) 2020-12-17 19:43:11 -05:00
eng Sync eng/common directory with azure-sdk-tools for PR 1335 (#13358) 2021-01-25 10:51:11 -08:00
samples [Key Vault] Add sample for working with Key Vault in web app (#13139) 2021-01-21 11:18:45 -08:00
sdk Increment version for monitor releases (#13355) 2021-01-25 10:20:49 -08:00
.gitattributes Use UNIX LF line endings everywhere, even on Windows (#10360) 2020-07-30 14:18:17 -07:00
.gitignore [KeyVault] - Enable node unit tests for KeyVault Administrator (#13230) 2021-01-19 07:40:51 -08:00
.prettierignore [Prettier] ignore recordings (#11297) 2020-09-16 14:17:52 -04:00
.prettierrc.json Standardize prettier configurations across the repo (#10416) 2020-08-04 16:31:27 -04:00
CONTRIBUTING.md fix link (#12188) 2020-10-30 15:18:53 -04:00
LICENSE Initial commit for copying files from azure-sdk-for-node 2018-08-27 13:58:16 -07:00
README.md Revert the formatting changes. (#11888) 2020-10-16 12:49:36 -07:00
SECURITY.md Replaced relative link with absolute links and remove locale (#11317) 2020-09-17 20:01:20 -07:00
dataplane.code-workspace Update karma test configuration for track2 packages (#13309) 2021-01-22 19:42:51 +00:00
gulpfile.ts Clean unnecessary scripts to enable Node 12 (#3037) 2019-05-21 09:26:49 -07:00
package.json Delete redandunt packages and move to the right yaml (#12739) 2020-12-02 16:47:44 -08:00
rush.json Azure Quantum SDK for Azure SDK for JS (#13345) 2021-01-23 00:18:03 +00:00
swagger_to_sdk_config.json bump autorest.typescript version (#12078) 2020-10-27 12:41:45 +08:00
tsconfig.json Use inlineSources to bundle source file contents inside map files (#7615) 2020-03-11 10:34:37 -07:00
tsconfig.package.json Update tsconfig for core packages (#6285) 2019-11-21 12:44:59 -08:00
tsdoc.json Standardization of our documentation comments (#12912) 2020-12-17 02:01:34 +00:00

README.md

Azure SDK for JavaScript

Packages Dependencies DependencyGraph

This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs.

Getting started

For your convenience, each service has a separate set of libraries that you can choose to use instead of one, large Azure package. To get started with a specific library, see the README.md file located in the library's project folder. You can find service libraries in the /sdk directory.

Each service might have a number of libraries available from each of the following categories:

Client: New Releases

New wave of packages that we are announcing as GA and several that are currently releasing in preview on npm. These libraries allow you to use and consume existing resources and interact with them. These libraries share a number of core functionalities found in the Azure Core package such as retries, logging, transport protocols, authentication protocols, etc. Learn more about these libraries by reading the guidelines that they follow.

You can find the most up to date list of all of the new packages on our page

NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.

Client: Previous Versions

Last stable versions of packages that have been provided for usage with Azure and are production-ready. These libraries provide you with similar functionalities to the Preview ones as they allow you to use and consume existing resources and interact with them, for example: upload a blob. They might not implement the guidelines or have the same feature set as the Novemeber releases. They do however offer wider coverage of services.

Management

Libraries which enable you to provision specific resources. They are responsible for directly mirroring and consuming Azure service's REST endpoints. You can recognize these libraries by mgmt or arm in their package names.

Need help?

Reporting security issues and security bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Contributing

For details on contributing to this repository, see the contributing guide.

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 repositories 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.

Impressions