зеркало из
1
0
Форкнуть 0
A Node.js SDK for connecting devices to Microsoft Azure IoT services
Перейти к файлу
Yoseph Maguire c8df3737c1
chore: adding conventional commits enforcement (#684)
* chore: adding conventional commits enforcement

* chore: add commitlint configuration

* chore: improving language
2020-01-31 13:38:32 -08:00
.github chore: adding conventional commits enforcement (#684) 2020-01-31 13:38:32 -08:00
build/tools Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
common Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
device Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
doc docs: updating readmes 2019-11-22 08:49:47 -08:00
e2etests Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
longhaultests chore (multiple): Adjust versions so hoisting is clean. (#656) 2019-11-19 15:27:21 -08:00
network_e2e chore(security vulnerabilities): npm audit fix (#607) 2019-08-16 11:03:08 -07:00
provisioning Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
security Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
service Bump package versions for release on 2020-01-16 (#678) 2020-01-16 12:26:25 -08:00
ts-e2e chore (multiple): Fix various linting problems. (#674) 2020-01-15 20:09:14 -08:00
vsts Adjust node version for windows builds down. (#641) 2019-10-03 20:46:50 -07:00
.gitattributes Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
.gitignore (fix) add setProvisioningPayload to the RegistrationClient interface. 2019-04-12 13:43:22 -07:00
.jshintignore [Node.js] Add code coverage reporting 2016-02-22 13:12:20 -08:00
.jshintrc fix(service client): service needs wrap eTag with double quotes (#613) 2019-09-09 14:08:03 -07:00
CODE_OF_CONDUCT.md Add code of conduct file 2017-10-17 15:43:27 -07:00
LICENSE Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
SECURITY.MD chore: Added Security MD file to the repo (#648) 2019-11-04 15:52:05 -08:00
commitlint.config.js chore: adding conventional commits enforcement (#684) 2020-01-31 13:38:32 -08:00
credscan_suppression.json fix(sdl): Add credscan suppression file 2018-10-30 17:49:21 -07:00
feature_matrix.md Update readmes and templates with support information and other main readme improvements 2018-03-16 11:00:32 -07:00
lerna.json move edge-e2e wrappers into Horton tree 2019-11-23 07:23:28 -08:00
lts_branches.png Update LTS document 2017-07-07 17:20:05 -07:00
mocha-reports.json Update mocha config to report e2e tests in VSTS builds 2018-08-25 17:26:57 -07:00
package-lock.json fix (azure-iothub): Added the property moduleContent #675. (#676) 2020-01-16 11:01:44 -08:00
package.json chore: adding conventional commits enforcement (#684) 2020-01-31 13:38:32 -08:00
readme-modules.md Fix wrong links and remove obsolete 'Future Changes' section 2019-03-29 14:45:32 -07:00
readme.md docs: minor patch on formatting (#660) 2019-11-22 10:30:01 -08:00
thirdpartynotice.txt Add license, readme, contribution guidelines and build files 2016-11-14 17:00:39 -08:00
tls_protocol_version_and_ciphers.md doc: Updating TLS md (#672) 2020-01-10 22:12:38 -08:00
tslint.json Update packages from npm audit. Also policy fixes. 2019-04-22 11:22:50 -07:00

readme.md

Build Status

Getting Started

Why Azure IoT?

Click here to learn how Azure IoT can empower the digital transformation of your organization.

New to Azure IoT Hub?

Introduction to Azure IoT Hub: Follow this guide to learn how to set up an IoT Hub and IoT Hub devices.

New to the Azure IoT Node.JS SDK?

Try a Device Sample: Create a basic Node.js application following one of the device client library samples provided.

Components

The Azure IoT Node.js SDK enables developers to create IoT solutions written in Node.js for the Azure IoT platform. It is composed of the following client libraries:

  • Device Client Library: to connect devices to Azure IoT Hub. API Reference
  • Service Client Library: enables developing back-end applications making use of Azure IoT Hub. API Reference
  • Provisioning Device Client Library: to connect devices to the Azure IoT Provisioning Service. API Reference
  • Provisioning Service Client Library: enables developing back-end applications making use of the Azure IoT Provisioning Service. API Reference

Samples

Device Library Samples Service Library Samples

npm Package List

Azure IoT Hub Device Client Libraries

Name npm package
Device Client npm version
MQTT Transport npm version
AMQP Transport npm version
HTTP Transport npm version

Azure IoT Hub Service Client Libraries

Name npm package
Service SDK npm version

Azure IoT Hub Device Provisioning Service: Device Client Libraries

Name npm package
Device Client npm version
MQTT Transport npm version
AMQP Transport npm version
HTTP Transport npm version
TPM Security Client npm version
x509 Security Client npm version

Azure IoT Hub Device Provisioning Service: Service Client Libraries

Name npm package
Service SDK npm version

Working from Source Code

If you want to modify or contribute changes to the SDK, then you can build the libraries following these instructions.

How to Contribute

If you encounter any bugs, have suggestions for new features or if you would like to become an active contributor to this project please follow the instructions provided in the contribution guidelines.

  • Have a feature request for SDKs? Please post it on User Voice to help us prioritize
  • Have a technical question? Ask on Stack Overflow with tag "azure-iot-hub"
  • Need Support? Every customer with an active Azure subscription has access to support with guaranteed response time. Consider submitting a ticket and get assistance from Microsoft support team
  • Found a bug? Please help us fix it by thoroughly documenting it and filing an issue.

Platform Compatibility

The Azure IoT SDK for Node.js supports the LTS and Current versions of the Node.js runtime.

Long Term Support

The project offers a Long Term Support (LTS) version to allow users that do not need the latest features to be shielded from unwanted changes.

A new LTS version will be created every 6 months. The lifetime of an LTS branch is currently planned for one year. LTS branches receive all bug fixes that fall in one of these categories:

  • security bugfixes
  • critical bugfixes (crashes, memory leaks, etc.)

No new features or improvements will be picked up in an LTS branch.

LTS branches are named lts_mm_yyyy, where mm and yyyy are the month and year when the branch was created. An example of such a branch is lts_07_2017.

Schedule1

Below is a table showing the mapping of the LTS branches to the package versions released

NPM Package Github Branch LTS Status LTS Start Date Maintenance End Date Removed Date
1.7.x lts_09_2018 Deprecated 2018-09-16 2019-09-16 2020-03-09
1.11.x lts_09_2019 Active 2019-09-09 2020-03-09 2020-09-19

1 All scheduled dates are subject to change by the Azure IoT SDK team.

Read More


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.

Microsoft collects performance and usage information which may be used to provide and improve Microsoft products and services and enhance your experience. To learn more, review the privacy statement.