-
Notifications
You must be signed in to change notification settings - Fork 2k
Updates client library, cleans up JS, fixes package.js so the tests run #698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,7 +20,5 @@ | |
| "uuid": "3.1.0", | ||
| "yargs": "8.0.2" | ||
| }, | ||
| "testDependencies": { | ||
| }, | ||
| "devDependencies": {} | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,18 @@ | ||
| { | ||
| "name": "nodejs-docs-samples-iot-mqtt-example", | ||
| "author": "Google Inc.", | ||
| "version": "0.0.1", | ||
| "description": "MQTT Example for Google Cloud IoT Core using NodeJS.", | ||
| "main": "cloudiot_mqtt_example_nodejs.js", | ||
| "license": "Apache-2.0", | ||
| "author": "Google Inc.", | ||
| "main": "cloudiot_mqtt_example_nodejs.js", | ||
| "name": "nodejs-docs-samples-iot-mqtt-example", | ||
| "scripts": { | ||
| "lint": "samples lint", | ||
| "pretest": "npm run lint", | ||
| "test": "samples test run --cmd ava -- -T 3m --verbose system-test/*.test.js" | ||
| }, | ||
| "dependencies": { | ||
| "@google-cloud/pubsub": "0.16.4", | ||
| "@google-cloud/nodejs-repo-tools": "2.2.1", | ||
| "@google-cloud/nodejs-repo-tools": "1.4.17", | ||
|
||
| "ava": "0.25.0", | ||
| "jsonwebtoken": "8.2.0", | ||
| "mqtt": "2.16.0", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the second param here would be an error. That's traditionally where you would use a
.catch():)