Merge pull request #4 from companieshouse/hotfix/S4-229-correct-repo-naming

hotfix/S4-229: Correct references to repo name in code.

Author: matthewdoreilly

README.md

@@ -14,7 +14,7 @@ The following snippet shows how to get up and running quickly using TypeScript.
 
 ```typescript
 
-import {createApiClient} from "ch-sdk-node";
+import {createApiClient} from "api-sdk-node";
 
 (async () => {
     const api = createApiClient("your-api-key");
@@ -28,7 +28,7 @@ import {createApiClient} from "ch-sdk-node";
 There is an alternative way of calling some of the services, which forces you to check for errors. It borrows concepts from the Either class found in functional programming.
 ```typescript
 
-import {createApiClient} from "ch-sdk-node";
+import {createApiClient} from "api-sdk-node";
 
 (async () => {
     const api = createApiClient("your-api-key");
@@ -56,7 +56,7 @@ From within this directory, run the following command to make symbolic links to
 
 Then from within your local project, simply link it with the following command
 
-    npm link ch-sdk-node
+    npm link api-sdk-node
 
 Note that if your local project is running within a Vagrant Virtual Machine, this command will need to be run on the VM.
 

package-lock.json

@@ -1,19 +1,16 @@
 {
-  "name": "ch-sdk-node",
+  "name": "api-sdk-node",
   "version": "1.0.0",
-  "description": "",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
+  "license": "ISC",
   "scripts": {
     "build": "tsc",
     "prebuild": "rm -rf dist/*",
     "test": "mocha",
     "lint": "eslint 'src/*.ts' 'src/**/*.ts' 'test/**/*.ts'",
     "lint:fix": "eslint 'src/*.ts' 'src/**/*.ts' 'test/**/*.ts' --fix"
   },
-  "keywords": [],
-  "author": "",
-  "license": "ISC",
   "dependencies": {
     "camelcase-keys": "~6.2.2",
     "request": "~2.88.0",