@kokuin/crypto-napi 0.7.0 → 0.7.1

package/lib/binding.d.ts

@@ -27,10 +27,10 @@ export type NapiBinding = {
     verifyBatch(items: Array<NapiVerifyParams>): Promise<Array<boolean>>;
     blake3Batch(params: NapiBindingBlake3BatchParams): Promise<Array<Uint8Array>>;
 };
-/** Why no native binding loaded, or `undefined` when one did. */
+/** Why no native binding loaded. `path` is absent when the binary's location did not resolve. */
 export type NapiLoadFailure = {
     reason: 'missing' | 'abi' | 'load';
-    path: string;
+    path?: string;
     cause?: unknown;
 };
 /** The platform suffix of the binary file name, such as `linux-x64-gnu` or `darwin-arm64`. */

package/lib/binding.js

@@ -36,7 +36,20 @@ function libc() {
 let cached;
 /** Load the native binding once per process. Never throws; reports why it could not load. */ export function loadNapiBinding() {
     if (cached != null) return cached;
-    const path = napiBindingPath();
+    let path;
+    try {
+        path = napiBindingPath();
+    } catch (cause) {
+        // A CJS bundle leaves `import.meta.url` undefined.
+        cached = {
+            binding: null,
+            failure: {
+                reason: 'load',
+                cause
+            }
+        };
+        return cached;
+    }
     if (!existsSync(path)) {
         cached = {
             binding: null,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kokuin/crypto-napi",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Strict asynchronous crypto provider backed by the Rust core through Node-API, falling back to @kokuin/crypto-node",
   "repository": {
     "type": "git",