@everystack/pg-tools 0.4.0 → 0.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/pg-tools",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Prebuilt PostgreSQL client tools (pg_dump/pg_restore) as an AWS Lambda layer for everystack db:backup",
   "license": "AGPL-3.0-only",
   "author": "Scalable Technology, Inc. <licensing@scalable.technology>",

package/src/index.ts

@@ -17,7 +17,7 @@
  */
 
 import { readFileSync } from 'node:fs';
-import { join } from 'node:path';
+import { join, dirname } from 'node:path';
 
 /** Shape of the committed `manifest.json` — the artifact's self-description. */
 export interface PgToolsManifest {
@@ -35,14 +35,24 @@ export interface PgToolsManifest {
   lock: { sha256: string; rpms: number };
 }
 
-// The package root, one level up from this source file. `__dirname` is the established asset-resolution
-// idiom in this (CommonJS) repo, and pg-tools is consumed as source at SST config-eval time — the zip
-// and manifest are real on-disk files in node_modules, no bundling has happened yet.
-const pkgRoot = join(__dirname, '..');
+// The package's REAL on-disk root — resolved via node module resolution of its OWN exported
+// manifest, never `__dirname`. SST 4.14+ bundles the dynamically-imported sst.config graph (and
+// this package with it), so `__dirname` resolves to the `.sst` bundle dir, not node_modules —
+// `join(__dirname, '..')` then reads a manifest that isn't there (ENOENT at config eval, the whole
+// deploy fails). `require.resolve` of the package specifier walks node_modules from wherever the
+// bundle lives and finds the real file. `require` is ambient: native under CommonJS (the tests, a
+// built dist) and provided by SST's ESM banner (`const require = createRequire(import.meta.url)`)
+// in the bundled config. Indirected through a variable so a bundler leaves it a runtime resolve
+// instead of trying to inline the target. (everystack: same __dirname-in-a-bundle class as the ops
+// handler; here it's the framework's own asset resolution.)
+const resolvePath = require.resolve;
+const pkgManifestPath = resolvePath('@everystack/pg-tools/manifest.json');
+const pkgRoot = dirname(pkgManifestPath);
 
-/** The artifact's manifest (major, arch, sha256, provenance). Read once at load. */
+/** The artifact's manifest (major, arch, sha256, provenance). Read once at load, from the resolved
+ *  real path. */
 export const manifest: PgToolsManifest = JSON.parse(
-  readFileSync(join(pkgRoot, 'manifest.json'), 'utf-8'),
+  readFileSync(pkgManifestPath, 'utf-8'),
 ) as PgToolsManifest;
 
 /** Absolute path to the vendored layer zip (arm64, PG `manifest.major`). */