envstash-cli 0.4.0 → 0.4.2

package/README.md

@@ -177,8 +177,9 @@ Monorepos can track nested paths by listing them explicitly:
 
 ## Opaque files (service-account keys, certs)
 
-A tracked name whose basename is not `.env` or `.env.*` is stored **whole**, as
-one encrypted file, rather than parsed into keys:
+A tracked name whose basename is not `.env`, `.env.*`, or `*.env` is stored
+**whole**, as one encrypted file, rather than parsed into keys — dotenv-shaped
+names, including the `.config/auth.env` convention, are parsed instead:
 
 ```json
 { "project": "demo-app", "files": [".env", ".config/service-account.json"] }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "envstash-cli",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "Git-style CLI for EnvStash — keep your .env files in sync with your cloud account.",
   "keywords": [
     "env",

package/src/blob.mjs

@@ -2,15 +2,17 @@ import { createHash } from 'node:crypto'
 import { basename } from 'node:path'
 
 /**
- * How a tracked name is classified when the cloud has no say yet: `.env` and
- * `.env.*` basenames are dotenv files parsed into keys; everything else — a
- * service-account JSON, a cert — is an opaque file stored whole. For names the
- * cloud already knows, its recorded kind wins; this function only decides the
- * kind of a file's first push.
+ * How a tracked name is classified when the cloud has no say yet: `.env`,
+ * `.env.*`, and `*.env` basenames are dotenv files parsed into keys — the
+ * trailing form covers the `.config/auth.env` convention, which is KEY=value
+ * content under a descriptive name. Everything else — a service-account JSON,
+ * a cert — is an opaque file stored whole. For names the cloud already knows,
+ * its recorded kind wins; this function only decides the kind of a file's
+ * first push.
  */
 export function isEnvName(name) {
   const base = basename(name)
-  return base === '.env' || base.startsWith('.env.')
+  return base === '.env' || base.startsWith('.env.') || base.endsWith('.env')
 }
 
 /**

package/src/ui.mjs

@@ -32,6 +32,22 @@ export const style = {
   cyan: wrap(36, 39),
 }
 
+/**
+ * `envs status | head` closes stdout after a few lines, and every write after
+ * that raises EPIPE — which Node treats as a crash, stack trace and all. A
+ * closed pipe is the reader saying "I have enough", not a failure, so leave
+ * the way a SIGPIPE-terminated process would: immediately and silently.
+ */
+for (const stream of [process.stdout, process.stderr]) {
+  stream.on('error', error => {
+    if (error?.code === 'EPIPE') {
+      process.exit(0)
+    }
+
+    throw error
+  })
+}
+
 export function out(message = '') {
   process.stdout.write(`${message}\n`)
 }