cloudflare-next-intl 0.10.0 → 0.10.2

package/bin/db_codegen.mjs

@@ -1,13 +1,15 @@
 #!/usr/bin/env node
-// Re-exec shim: `cfni-db-codegen` now lives in cloudflare-next-intl-db,
+// Re-exec shim: `cfni-db-codegen` now lives in cloudflare-next-intl-db-codegen,
 // installed as this package's dependency. Kept here so existing consumers'
 // `npx cfni-db-codegen` invocations keep working with no changes needed.
+import { createRequire } from 'node:module';
 import { fileURLToPath, pathToFileURL } from 'node:url';
 import { dirname, join } from 'node:path';
 
-// Resolve via the package's root export (".") — its exports map doesn't
-// declare "./package.json", so that can't be resolved directly. The root
-// export ("dist/src/index.js") sits two directories below the package root.
-const indexPath = fileURLToPath(import.meta.resolve('cloudflare-next-intl-db'));
-const dbPackageRoot = join(dirname(indexPath), '..', '..');
-await import(pathToFileURL(join(dbPackageRoot, 'bin', 'db_codegen.mjs')).href);
+// cloudflare-next-intl-db-codegen declares no "exports" map, so its
+// package.json (and therefore its package root) resolves directly —
+// unlike the runtime db package, this one isn't trying to restrict its
+// public surface to a curated set of subpaths.
+const pkgPath = createRequire(import.meta.url).resolve('cloudflare-next-intl-db-codegen/package.json');
+const codegenPackageRoot = dirname(fileURLToPath(pathToFileURL(pkgPath)));
+await import(pathToFileURL(join(codegenPackageRoot, 'bin', 'db_codegen.mjs')).href);

package/bin/db_install_exec.mjs

@@ -1,13 +1,15 @@
 #!/usr/bin/env node
-// Re-exec shim: `cfni-db-install-exec` now lives in cloudflare-next-intl-db,
+// Re-exec shim: `cfni-db-install-exec` now lives in cloudflare-next-intl-db-codegen,
 // installed as this package's dependency. Kept here so existing consumers'
 // `npx cfni-db-install-exec` invocations keep working with no changes needed.
+import { createRequire } from 'node:module';
 import { fileURLToPath, pathToFileURL } from 'node:url';
 import { dirname, join } from 'node:path';
 
-// Resolve via the package's root export (".") — its exports map doesn't
-// declare "./package.json", so that can't be resolved directly. The root
-// export ("dist/src/index.js") sits two directories below the package root.
-const indexPath = fileURLToPath(import.meta.resolve('cloudflare-next-intl-db'));
-const dbPackageRoot = join(dirname(indexPath), '..', '..');
-await import(pathToFileURL(join(dbPackageRoot, 'bin', 'db_install_exec.mjs')).href);
+// cloudflare-next-intl-db-codegen declares no "exports" map, so its
+// package.json (and therefore its package root) resolves directly —
+// unlike the runtime db package, this one isn't trying to restrict its
+// public surface to a curated set of subpaths.
+const pkgPath = createRequire(import.meta.url).resolve('cloudflare-next-intl-db-codegen/package.json');
+const codegenPackageRoot = dirname(fileURLToPath(pathToFileURL(pkgPath)));
+await import(pathToFileURL(join(codegenPackageRoot, 'bin', 'db_install_exec.mjs')).href);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cloudflare-next-intl",
-  "version": "0.10.0",
+  "version": "0.10.2",
   "description": "Optimized Next Intl Package Special for App Router and Cloudflare",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -358,7 +358,8 @@
   "homepage": "https://github.com/demian-ilnytskyi/cloudflare-next-intl#readme",
   "dependencies": {
     "@microsoft/clarity": "^1.0.2",
-    "cloudflare-next-intl-db": "^0.1.1",
+    "cloudflare-next-intl-db": "^0.2.1",
+    "cloudflare-next-intl-db-codegen": "^0.1.1",
     "jose": "^6.2.8",
     "sharp": "^0.34.5 || ^0.35.0"
   },