Merge pull request #16 from well-known-components/feat/remove-bin

feat: remove bin
well-known-components · Jun 14, 2022 · a63a99a · a63a99a
2 parents 010fe04 + 57bbdb7
commit a63a99a
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 152 deletions.
diff --git a/README.md b/README.md
@@ -79,16 +79,16 @@ for await (const row of database.streamQuery<TableType>(query, { batchSize: 1000
 
 ## Migrations
 
-If you want to have migrations for your database, this component allows for the use of [node-pg-migrate](https://github.com/salsita/node-pg-migrate) as a proxy. For this you'll need to:
+If you want to have migrations for your database, this component uses [node-pg-migrate](https://github.com/salsita/node-pg-migrate) as a proxy. For this you'll need to:
 
 - Supply the necessary [runner options](#create) on your component creation. You'd normaly want to use 'up' as a migration direction
-- For creating new migrations or any other type of interaction with the [node-pg-migrate](https://github.com/salsita/node-pg-migrate) binary, you can use `pg_component`. This binary is a proxy for node-pg-migrate adding some opinionated options that can be overriden. To use:
+- For creating new migrations or any other type of interaction you can use the [node-pg-migrate](https://github.com/salsita/node-pg-migrate) binary. To use we recommend:
 
 **package.json**
 
 ```json
 "scripts": {
-  "migrate": "pg-component migrate"
+  "migrate": "node-pg-migrate --database-url-var PG_COMPONENT_PSQL_CONNECTION_STRING --envPath .env -j ts --tsconfig tsconfig.json"
 }
 ```
 

diff --git a/package.json b/package.json
@@ -46,7 +46,6 @@
   "peerDependencies": {
     "@well-known-components/interfaces": "^1.1.0"
   },
-  "bin": "./dist/exec.js",
   "files": [
     "dist"
   ]

diff --git a/src/exec.ts b/src/exec.ts
diff --git a/test/exec.spec.ts b/test/exec.spec.ts