fix: add the README, remove unnecessary files

.openapi-generator-ignore

@@ -3,4 +3,5 @@ README.md
 git_push.sh
 package-lock.json
 package.json
-yarn.lock
+yarn.lock
+tsconfig.esm.json

README.md

@@ -0,0 +1,53 @@
+<!-- TEXT_SECTION:header:START -->
+<h1 align="center">
+Gentrace Browser SDK
+</h1>
+<p align="center">
+  <a href="https://github.com/gentrace/gentrace-openapi/blob/master/LICENSE">
+    <img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="Gentrace is released under the MIT license." />
+  </a>
+  <a href="https://github.com/gentrace/gentrace-openapi/actions/workflows/release-please.yaml">
+    <img src="https://github.com/gentrace/gentrace-openapi/actions/workflows/release-please.yaml/badge.svg" alt="Release Github action status" />
+  </a>
+</p>
+<!-- TEXT_SECTION:header:END -->
+
+
+The Gentrace browser library provides code for developers to submit feedback to Gentrace servers from the browser. Most of the code in this library is generated from our [OpenAPI specification](https://github.com/gentrace/gentrace-openapi).
+
+**Important note: this library is meant for client-side usage.**  We are not actively supporting this package on server-side JavaScript environments.
+
+## Installation
+
+```bash
+$ npm install @gentrace/browser
+```
+
+## Usage
+
+The library needs to be configured with your account's client token, which is available on the [website](https://staging.gentrace.ai/t/<slug>/settings/client-tokens). We recommend setting it as an environment variable. Do **not** use an API key. The feedback routes will not authorize correctly and you risk leaking your credentials in your client bundles.
+
+Here's an example of initializing the library with the client token loaded from an environment variable and creating a completion:
+
+```javascript
+TODO: insert code
+```
+
+Check out the [full API documentation](https://docs.gentrace.ai/docs/api-reference?platform=browser) for examples of all the available functions.
+
+### Request options
+
+All of the available API request functions additionally contain an optional final parameter where you can pass custom [axios request options](https://axios-http.com/docs/req_config), for example:
+
+
+```javascript
+TODO: insert code
+```
+
+### Error handling
+
+API requests can potentially return errors due to invalid inputs or other issues. These errors can be handled with a `try...catch` statement, and the error details can be found in either `error.response` or `error.message`:
+
+```javascript
+TODO: insert code
+```

package.json

@@ -18,7 +18,7 @@
     "build": "run-s clean compile",
     "bump-patch": "./scripts/bump-patch",
     "clean": "rm -rf dist",
-    "compile": "tsc --outDir dist -d index.ts"
+    "compile": "tsc -p tsconfig.json"
   },
   "dependencies": {
     "axios": "^0.27.2"

tsconfig.json

@@ -7,12 +7,7 @@
     "outDir": "dist",
     "rootDir": ".",
     "moduleResolution": "node",
-    "typeRoots": [
-      "node_modules/@types"
-    ]
+    "typeRoots": ["node_modules/@types"]
   },
-  "exclude": [
-    "dist",
-    "node_modules"
-  ]
+  "exclude": ["dist", "node_modules"]
 }