dispatch-node-sdk - npm Package Compare versions

Comparing version 1.4.1 to 1.4.2

dist/lib/analytics.js

		@@ -13,2 +13,6 @@ 'use strict';
		UNABLE_TO_ADD_TECH: 'add_tech_error', // 'Unable to add tech'
		APPOINTMENT_SCHEDULED: 'appointment_scheduled', // Appointment scheduled
		APPOINTMENT_ENROUTE: 'appointment_enroute', // en route to appointment
		APPOINTMENT_STARTED: 'appointment_started', // Appointment started
		APPOINTMENT_CANCELED: 'appointment_canceled', // Appointment started

		@@ -15,0 +19,0 @@ // Jobs

lib/analytics.js

		@@ -8,2 +8,6 @@ const Analytics = {
		UNABLE_TO_ADD_TECH: 'add_tech_error', // 'Unable to add tech'
		APPOINTMENT_SCHEDULED: 'appointment_scheduled', // Appointment scheduled
		APPOINTMENT_ENROUTE: 'appointment_enroute', // en route to appointment
		APPOINTMENT_STARTED: 'appointment_started', // Appointment started
		APPOINTMENT_CANCELED: 'appointment_canceled', // Appointment started

		@@ -10,0 +14,0 @@ // Jobs

package.json

		{
		"name": "dispatch-node-sdk",
		"version": "1.4.1",
		"version": "1.4.2",
		"description": "High- and low-level libraries for interacting with the Dispatch API",
		@@ -5,0 +5,0 @@ "main": "dist/lib/index.js",

README.md

		@@ -282,1 +282,12 @@ Dispatch JavaScript SDK
		```


		## Publishing

		Once you have commited all your changes and pushed to your respective branch, the steps to publishing to NPM are as follows:
		1. Update the package version in `package.json`
		2. Run `npm publish`
		3. Commit your changes with a comment describing the updated version eg. "Bumped version to 1.2.3"
		4. Tag the release with the respective version, eg.
		* `git tag 1.2.3`
		* `git push origin --tags`

New alerts