Show concrete examples of library usage

diff --git a/README.md b/README.md
index 70c261fdb86247b3af116185e4ccd82f7eabb952..bb45c47c0c7c0a51f681a2af8debf414983ec0ed 100644 (file)
--- a/README.md
+++ b/README.md
@@ -52,6 +52,50 @@ npm i -g @ardislu/envpass
 envpass decrypt -is -- node index.js
 ```
 
+## Library usage
+
+To fine-tune usage, you can call the `encrypt` or `decrypt` functions in code.
+
+### Decrypt and set variables in `process.env`
+
+The code below is equivalent to `import '@ardislu/envpass/decrypt'`:
+
+```javascript
+import { decrypt } from '@ardislu/envpass';
+
+await decrypt({
+  outFile: false,
+  injectInProcess: true,
+  silent: true
+});
+```
+
+### Set a specific port for the passkey bridge
+
+The same option is available for `decrypt` as well.
+
+```javascript
+import { encrypt } from '@ardislu/envpass';
+
+await encrypt({
+  getPrfOptions: { port: 9999 }
+});
+```
+
+### Manually abort the passkey flow
+
+The same option is available for `decrypt` as well.
+
+```javascript
+import { encrypt } from '@ardislu/envpass';
+
+const controller = new AbortController();
+const encryptionPromise = encrypt({
+  getPrfOptions: { signal: controller.signal }
+});
+controller.abort();
+```
+
 ## CLI reference
 
 ```
@@ -94,20 +138,6 @@ Options:
   -h, --help               display help for command
 ```
 
-## Library reference
-
-```javascript
-import { encrypt, decrypt } from '@ardislu/envpass';
-
-await encrypt({
-  // ...
-});
-
-await decrypt({
-  // ...
-});
-```
-
 ## Why?
 
 Encrypting your `.env` is defense in depth that helps to mitigate supply chain attacks where an attacker has injected code to your local environment. Most passkey implementations require active user participation to decrypt, which will help prevent attackers from getting secrets via passive extraction by scripts.